Re[2]: Announcing: Project Ridley

[andrey <aka_ bk ru>]

> Gustavo J. A. M. Carneiro wrote:
> > On Mon, 2005-08-22 at 16:10 +0200, Christian Neumair wrote:
> > 
> >>Am Montag, den 22.08.2005, 13:37 +0200 schrieb Rodrigo Moya:
> >>
> >>>there is no reason to force us to do GNOME 3.0, but since many GNOME
> >>>libraries will be disappearing with Ridley, we might want to call it
> >>>3.0, so that we don't have to maintain the old libraries around.
> >>>
> >>>Also, as we deprecate most stuff in libgnome/libgnomeui, we might want
> >>>to think about the role of those libraries. I would suggest we use them
> >>>for having high-level desktop oriented things in one place, like, for
> >>>instance, talking to the panel/window manager/file manager/etc,
> >>>notifications, services (libgnomeservice), libegg, icon theme.
> >>>Thus, as we reduce the number of generic libraries by getting them into
> >>>GTK+, we also reduce the number of specific, high-level libraries, by
> >>>putting them into libgnome/libgnomeui. Since we'll always need these
> >>>high-level libraries, instead of killing libgnome*
> >>>(http://live.gnome.org/LibgnomeMustDie), it might be much better to
> >>>change its purpose.
> >>>
> >>>All those would be enough to justify a GNOME 3.0 :)
> >>
> >>Does this also mean that we can get rid of deprecated API like GtkTree,
> >>GtkCList or GtkFileSelector?
> > 
> > 
> >   Maybe just moving deprecated widgets to a separate library, like
> > libgtk2.0-compat.la, would be a better solution?  We'd get well
> > maintained applications to avoid linking to this library, while at the
> > same time keeping it around for those apps that just need it and whose
> > authors are stuburn enough to not want to update.
> So let those apps depend on GTK+-2.x, like many depend on 1.2 now. 
> Moving widgets to separate library will require some changes in related 
> apps anyway.
> 
> 	Olexiy

i suppose will be better - to make Ridley Project separated from 
deprecated libraries (GTK+-2.x,1.2 ...), so 
old apps will use deprecated libraries, new applications - new libraries.
if apps-developer want to porting apps from old libraries to new -
 he spend some time anyhow.
This is a "backward compatibility without backward compatibility".