Hello
What exactly is the current situation with the various graphics related components? Mag appears to be a nitpicker replacement and dope ran under nitpicker. Goos is a new low level framework that is used by mag?
Then there are various fb* like fb-drv and fbterminal.
What is the current direction of the graphics and GUI components, how do they stack and what is the preferred way to get them to run?
Are they documented somewhere?
- Taru Karttunen
Hi,
On Sun Aug 08, 2010 at 19:45:09 +0300, Taru Karttunen wrote:
What exactly is the current situation with the various graphics related components? Mag appears to be a nitpicker replacement and dope ran under nitpicker. Goos is a new low level framework that is used by mag?
Goos is the interface that is either implemented or used by other components, or both. Mag as well as Dope implement the interface. Mag provides the full windowing as well as the framebuffer interface, as where Dope only provides the framebuffer one.
Then there are various fb* like fb-drv and fbterminal.
fb-drv contains the hardware framebuffer driver and exports it via the Goos interface. fbterminal is a terminal that uses a framebuffer from any provider.
What is the current direction of the graphics and GUI components, how do they stack and what is the preferred way to get them to run?
They can be stacked as you want. See the screenshots on the website (http://os.inf.tu-dresden.de/L4Re/ss/mag+dope+con.png).
Are they documented somewhere?
There are the doxy-docs and there's an example configuration in l4/conf/examples/
Adam
l4-hackers@os.inf.tu-dresden.de