|Site sponsored by IGEL|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[directfb-dev] Re: Discussion
Quoting Wood, David (DWood@daedalcorp.com): > Along this line, I've noticed it mentioned in the DirectFB todo list that > multi-application support is coming, won't this require massive changes to > the existing api and code-base? Would it be simpler to treat DirectFB as a > video subsystem and write a multi-application window management system on > top of it? Of course it would mean adding yet another api for application > development. DirectFB has two main parts: the core and the interfaces. The API is defined by the interfaces, they access the core functions to create core objects like CoreSurface or CardState. The external API has been designed to remain unchanged (maybe some feature additions or fixes) while the core can be replaced by a core that pulls multiple applications together and handles locking and synchronization. Implemented via IPC (master/slaves) it should perform much better than client/server oriented systems. All programs can access the graphics hardware, input devices are handled by the master that dispatches the input events to all slaves and itself, of course. -- Denis Oliver Kropp ( convergence ) ( integrated media gmbh ) -- Info: To unsubscribe send a mail to email@example.com with "unsubscribe directfb-dev" as subject.