From: John P. <jo...@ma...> - 2002-07-01 15:42:36
|
Hello, I used to hack at Gaim's applet code way back before I got caught up in other things (Yes I was the one who wrote the horribly long variables and files names, I have since learned my lesson ;-) Anyway, I was looking at updating the applet stuff for Gnome 2.0. Has anyone been working on this? I started working on it unfortunatly I can't compile Gaim because I am working on a pure Gtk2.0/Gnome2.0 platform. The m4 macros always choke. As a start it doesn't realy matter since I have already created most of the functionality of the old applet in a seperate applet project with the one cavet that it is not hooked up with Gaim yet. I don't know if you guys plan on going completely Gtk+ 2.0 and ditch the old 1.0 stuff but if you did it would be realy nice to ditch the old model of hundreds of #ifdef's and instead go with a layered approach. In this way a core library (gaim-common) with hooks to get the Gtk-2.0 top level widgets would be used in conjunction with a stub loader. The stub loader would have the main Gtk+ event loop and simply call the library to display the widget. For those who want GNOME applet functionality a seperate applet project, which is also a stub loader, would set itself up with the library, register a status callback(signal/slot) with the library (for changing icons on the applet) and let Gaim do its thing. This would allow people to have just the pure Gtk+ Gaim and get the applet if they want Gnome functionality. (This would also fix much of my Debain/Ximian conflicts which refuses to install the gnome-gaim build without first ripping out the gaim build and a lot of associated libraries in the process). This is just a suggestion and I'm offering to help. I realy want to get to the point where I can just rely on Gnome2.0 as a stand alone desktop and not have to rely on the 1.0 libraries. I though Gaim would be a cool first step. Its up to you guys. Thanks. -- J5 |
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 |
From: Nathan W. <fac...@fa...> - 2002-07-02 22:27:09
|
On Tue, Jul 02, 2002 at 04:33:00PM -0400, John Palmieri wrote: > 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.= =20 > To this end someone even mentioned Gaim on Slashdot as a deciding factor > for switching.=20 >=20 > 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.=20 =2E/configure --enable-gtk2 It works, for the most part, last time I checked. I think any work you want to do in this area can be contained in the existing framework. Remember, however, that the developers are currently re-writing large sections of code, including the UI, getting it ready for Gtk-2.0, among other things.=20 I would suggest joining us in #gaim on irc.openprojects.net, and discussing things there. --=20 Nathan Walp || fac...@fa... GPG Fingerprint: || http://faceprint.com/ 5509 6EF3 928B 2363 9B2B DA17 3E46 2CDC 492D DB7E |