On Fri, Feb 14, 2003 at 05:00:04PM +0100, Jérôme Marant wrote: > En réponse à Sven Luther <[EMAIL PROTECTED]>: > > > > > I sure must continue packaging lablgtk 1.2 until nobody uses it, > > > > unless > > > > cameleon is ported to lablgtk 2., that is. > > > > > > I'd advice that you keep it at least one year. > > > > But maybe i can rename it to lablgtk1.2 or to lablgtk_old or something > > ? > > How about doing like libgtk : lablgtk1.2 and lablgtk2?
Well, libgtk is libgtk1.2 and libgtk2.0. But still, libgtk2.0 is at version 2.2.x right now ... > > > > Are there other apps depending on lablgtk 1.2 around, and if there > > > > are, > > > > does any of them also use camlimage ? > > > > > > There are at least probably some third party application that still > > > use it. (I'd say that every GTK app use it currently). > > > > Yes, probably, but i think it is trivial to adapt them, i adapted my > > app > > in 5 minutes or so, a bit more for removing the opengl rendering path > > i > > didn't use (no easy way to write text, nor circles, and i was doing 2D > > anyway) and only keep the Gdk one. > > If you volonteer to adapt every third party app, everything's alright > then :) No, i think not. BTW, i have tried running lablgtk2 apps on a machine with only a S3 Trio as graphic card with 4Mo of memory, and they don't launch, well, there is cpu acitivy and lot of swapping, but they don't appear on the screen. I am running at 16bpp and 1024x768, which makes 1.5Mo of video ram only. Anyway, i guess it is good to keep lablgtk1.2 around also for older slower machines. Friendly, Sven Luther
