On 3/5/07, Denis Oliver Kropp <[EMAIL PROTECTED]> wrote: > Mike Gibson schrieb: > > I've just completed a working Qt/Embedded (3.3) Gfx driver for > > DirectFB. This shouldn't be confused with the qt on directfb project, > > which seems to be meant to work within the windowing system of > > DirectFB. This project uses the fullscreen mode of DirectFB. > > Qt/Embedded has it's own windowing system. > > I had a look at this minimal port :) > > What about implementing some accelerated functions? > > I guess this would require the QtE core to render > directly into the DirectFB Surface as well.
Yeah. This is problem with how QtE wants to do things. It wants a preallocated section of RAM to write everything to, which shouldn't be changes as far as I can tell. Otherwise, I have to reimplement quite a bit of code in QGfxRaster that I wouldn't even know how to start. The real question still comes down to that I'm maintaining two copies of the framebuffer, one in my driver and the real one handled by DirectFB. If there were some way for me to keep those synced (or eliminate one) that would allow for accelerated operations. Ideas are welcome. The docs for this area of QtE aren't very good. Playing with accelerations is on the list of to do's once I get the keyboard and mouse drivers working. Mike Gibson _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
