From: John P. <jo...@ma...> - 2002-07-02 20:32:05
|
The problem with going with a partial port (#ifdef GTK2) is that the build scripts are still searching for 1.0 macros. I don't see Gnome 2.0 as bugg apart from some of the behaviors of individual apps. I do see it as a lot faster(and nicer looking) than 1.0 expecialy Nautilus. And Gaim would be mostly Gtk+ which has been 2.0 longer than the Gnome libs. Also the Gtk+2.0 API and build scripts are just more sain. Many people have refused to switch to 2.0 until their favorite apps and applets appear on the platform. A chicken and the egg problem at best. To this end someone even mentioned Gaim on Slashdot as a deciding factor for switching. How about this. I temporarily fork Gaim, rewrite the build scripts and proceed to get it to compile on my pure 2.0 machine. At some point it becomes usable I show you guys, you sign off on it if you like it and it is released as a intermediate 2.0 build. At some point in the future when Gtk/Gnome 2.0 is blessed as usable the codebases can merge. I know forking can be bad for a project but that is usualy when done after a big flame fest :-). Tell me what you think. -- J5 On Mon, 2002-07-01 at 20:20, Justin wrote: > My only beef with that, is that Gnome 2.0 is far from a stable thing yet, so > hardly anybody will be dumping the 1.0 libraries or even upgrading to Gnome > 2.0 (and sticking to it) for a while... > > I really want to check out Gnome because KDE is simply driving me crazy > lately... but.. eh.. I dont think I'd have much more fun in Gnome, sadly.. > > I hope that a Gnome 2.0.1 release will be out soon to fix alot of the big > problems and by that time more people will have made their apps gtk+ 2 > compatible... > > -Justin |