x in om2007.2
sten at kvamme.se
Sun Jul 27 15:24:41 CEST 2008
From my point of view it's all about how many layers of abstraction
I want to have between my app and my screen. X11 is certainly
introducing a fat layer, and so is GTK+. The most extreme case I have
seen is Chuck Moore's Colorforth, where you have no layers at all,
you are dealing with the screen memory directly, there you can talk
Joe Armstrong made that clear to me with his Erlang GUI ex11. The app
is talking to the X11 server without additional layer than X11
itself. Made me realize that X11 isn't that bad, it's all about
layers piling up that is slowing things down.
On Jul 27, 2008, at 9:52 , sparky mat wrote:
> kinda new here. i noticed that om2007.2 and asu are slower than qtopia
> (the one from trolltech, not the x11 port). i presume its partly
> because X is being used.
> would it make sense to alter gtk+ for om2007.2 to directly write to
> screen? and prolly add some window management i guess.. or make X a
> lot lighter.. are we using X.org or X11. what about TinyX?
> i'm not too familiar with most of the tech mentioned above, so I
> apologise if i'm coming across as idiotic.
> devel mailing list
> devel at lists.openmoko.org
More information about the devel