Re: First deprecate APIs and then remove them in the next major version

From: Paul Davis <paul linuxaudiosystems com>
To: Emmanuele Bassi <ebassi gmail com>
Cc: Salvatore De Paolis <iwkse-ml gmx com>, GTK Devel List <gtk-devel-list gnome org>
Subject: Re: First deprecate APIs and then remove them in the next major version
Date: Sat, 23 Dec 2017 10:47:08 -0500

On Sat, Dec 23, 2017 at 9:06 AM, Emmanuele Bassi <ebassi gmail com> wrote:

Unsurprisingly, considering that the whole UI is completely custom and
>
> http://libremusicproduction.com/news/20171221-lsp-plugins-version-110-released-farewall-gtk

using a generic desktop toolkit would have made their lives miserable.

actually, my impression from interactions with the author is that GTK didn't make their life miserable at all.

however, the issues that have been mentioned before regarding host/plugin toolkit interactions did make their (and users') lives miserable, hence the switch.

Follow-Ups:
- Re: First deprecate APIs and then remove them in the next major version
  - From: Christian Schoenebeck

References:
- First deprecate APIs and then remove them in the next major version
  - From: Sébastien Wilmet
- Re: First deprecate APIs and then remove them in the next major version
  - From: Christian Hergert
- Re: First deprecate APIs and then remove them in the next major version
  - From: Salvatore De Paolis
- Re: First deprecate APIs and then remove them in the next major version
  - From: Emmanuele Bassi

[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]