Re: X and Matchbox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael 'Mickey' Lauer schreef: > Tim Newsom wrote: >> Note, when I talk about themes I am not talking about just changing the >> graphics but also the locations of various rendered buttons and >> interface elements in order to find optimal locations. > > The only GUI toolkit that makes this possible is the Enlightenment > EFL. Unfortunately it was not mature enough at the point where the > OpenMoko team had to choose their base toolkit. You could let the theme specify new .glade files, which makes reording buttons possible, even with gtk+. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFbKaIMkyGM64RGpERAk9HAJ9Mob3D5hhRRfWfME/HHbo1t45sqACcDrRw 9w2A3RNDii8YTR8hxSnwxgc= =h8Gy -END PGP SIGNATURE- ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re[2]: X and Matchbox
Tim Newsom wrote: > Note, when I talk about themes I am not talking about just changing the > graphics but also the locations of various rendered buttons and > interface elements in order to find optimal locations. The only GUI toolkit that makes this possible is the Enlightenment EFL. Unfortunately it was not mature enough at the point where the OpenMoko team had to choose their base toolkit. Regards, :M: -- Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: X and Matchbox
Related to this, was my question about themes. I will have to check out the abilities of the gtk theme engine in regards to this, but I have an interest in porting the LCARS theme from the 770 or other themes to the phone. It would seem to me (and maybe I don't understand as well as I thought I did) that the ability to theme the interface could help usability studies / testing of new phone interface designs. The ability to design and quickly switch between different designs would be of importance in that situation. Note, when I talk about themes I am not talking about just changing the graphics but also the locations of various rendered buttons and interface elements in order to find optimal locations. I am not sure how far you could go with it, but if its easy to do then you know people will jump on it. --Tim ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: X and Matchbox
Pedro Aguilar wrote: > I have several questions regarding the graphics support. > As far as I know the Neo uses X and Matchbox as Window Manager. Correct. > Do you know if the video driver that X uses has been specifically > developed/modified for this platform? It is the standard xorg-x11-kdrive server. > X can be adapted for embedded devices (like in the Zaurus) for being as > light as possible. In the Neo how much memory and footprint does X needs? I didn't have a chance to write down numbers yet. Will do when I'm working on the hardware again. > Does OpenMoko support Frame Buffer? > Using the FB could be interesting because some graphic operations could be > improved. We don't recommend direct frame buffer access, but if you absolutely need to do it to squeeze out the last bits of performance, then you're free to halt X and talk to /dev/fb. We rather want to support SDL which plays nicely with X. > Have you ever tested it with other Window Managers? I know Matchbox was > specifically designed for this kinf of devices, but WindowMaker and > Blackbox, for example, are very light and fast too (and they support > virtual desktops that could be nice to have). We don't have special requirements to a window manager, since most of the UI is drawn by Gtk and there are almost no window decorations -- this is the primary use case for MatchBox. Virtual Desktops is -- as the name says -- a desktop paradigm. It was designed for when you have a lot of application windows concurrently on a screen which all have dedicated geometry and you want to save state when switching between these desktops. I don't think this will be of much use on a phone since we run applications one-window-full-screen on OpenMoko. -- Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
X and Matchbox
Hi, I have several questions regarding the graphics support. As far as I know the Neo uses X and Matchbox as Window Manager. Do you know if the video driver that X uses has been specifically developed/modified for this platform? X can be adapted for embedded devices (like in the Zaurus) for being as light as possible. In the Neo how much memory and footprint does X needs? Does OpenMoko support Frame Buffer? Using the FB could be interesting because some graphic operations could be improved. Have you ever tested it with other Window Managers? I know Matchbox was specifically designed for this kinf of devices, but WindowMaker and Blackbox, for example, are very light and fast too (and they support virtual desktops that could be nice to have). Thanks! Pedro Aguilar ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community