On 6/1/06, Hannes Mayr <[EMAIL PROTECTED]> wrote: > Attilio Fiandrotti wrote: > > Hannes Mayr wrote: > >> Attilio Fiandrotti wrote: > >> > >>> Eddy Petrişor wrote: > >>> > >>>> On 6/1/06, Hannes Mayr <[EMAIL PROTECTED]> wrote: > >>>> > >>>>> Hello, > >>>>> > >>>>> is there a way to patch a GTK 2.6 version to add DirectFB support? > >>>>> Looking to the CVS I can only checkout the HEAD for the current GTK > >>>>> version or the next possible tag is 2_0_9 for GTK 2.0.9 which I'm > >>>>> currently using. Is there no patch available for a GTK version between > >>>>> 2.0.9 and 2.8? > >>>> > >>>> Attilio Fiandrotti has a patch against 2.8. Follow this thread: > >>>> http://lists.debian.org/debian-gtk-gnome/2006/05/msg00082.html > >>>> > >>> that's a GDKDFB backend backported from 2.9 to 2.8 plus patchfile for > >>> GTK+ 2.8.17: if you're looking for GTK 2.6 to get rid of cairo, this > >>> doesn't apply > >>> > >> Yep, that's exactly what I want...not using cairo :-) > >> So, there is absolutely no way to have a working directfb GDK backend > >> for 2.6? > > > > I guess updating GDKDFB 2.0.9 to 2.6.x while backporting bugfixes from > > 2.9.x series is possible, but i don't know if it's really worth it. > > A question: why don't you want to use GTK 2.9 ? is it because of the > > size of the resulting set of libraries (gtk+gdk+cairo) ? > > > > I use GTK on an embedded board. The size is not really the main problem, > more I'm worried about the performance/speed and the memory usage. At > the moment running with GTKDFB 2.0.9 the performance is acceptable, but > I'm having odd problems with treeviews eating up memory (possible memory > leak which I'm unable to locate). > But though I'll give gtk with cairo a try, maybe it works. >
Yes there are a number of memory leaks in the port is is still unstable. I'm working on fixing issues and should have time within the next month to work seriously on cairo/gdk. With that said if you can identify the major bugs that are show stoppers for you then I'll be happy to fix them and get the port stable enough for your use. But your going to have to do the grunt work of isolating the issues at least down to a reproducible bug report. I think right now the port has less then 100 serious bugs in it with less then 10 effecting any particular usage situation so overall it does have quite a few problems but solving the ones that effect a particular person is resonable and doable. Plan on about 2-3 months of bug fixing to meet your needs. Mike > > Hannes > > > _______________________________________________ > directfb-dev mailing list > [email protected] > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev > _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
