On Mon, 2002-10-21 at 05:36, Andreas Kotes wrote: > Hi! > > * Andreas Kotes <[EMAIL PROTECTED]> [20021019 15:55]: > > * Sven Neumann <[EMAIL PROTECTED]> [20021019 15:30]: > > > Andreas Kotes <[EMAIL PROTECTED]> writes: > > > > In your place, I'd start digging through the gnome/gtk libraries, > > > > isolation the (drawing) code which isn't specific to gnome/gtk and > > > > extract it. This code should be send as a patch for libdirectfbee, and > > > > afterwards, gnome/gtk (or e.g. Qt, for that) should (when compiled for > > > > DirectFB, the #ifdef .. #else .. #endif game ..) use these routines > > > > instead of the current code. Reduces code size in gnome/gtk and takes > > > > care of getting a reasonable code base for libdirectfbee. > > > > > > sorry, but I don't follow you here. All the GTK+/GNOME drawing code > > > is abstracted in GDK. GDK itself is split into backend-dependant and > > > backend-independant parts and this is _not_ done using stuff like > > > #ifdef ... #else ... #endif. What are you talking about? > > > > oops, seems like I was just babbling at this place, albeit I should have > > known better. wrote the mail after a quite short night .. sorry for any > > confusion. the #ifdef etc stuff would work with other toolkits, thou. > > wicked thought: why not port Qt drawing to GDK and drop native drawing > support in Qt? ;) > Are the widget functions in the KDE libraries or in the Qt libraries? How hard would it be to port the widget library from KDE/Qt to use the GTK widget library?
Karl Bowden -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
