Embedded GTK+ fragmented? [LWN.net]

Embedded GTK+ fragmented?

Posted Jan 26, 2007 15:42 UTC (Fri) by debacle (subscriber, #7114)
Parent article: Mobile Leaders Around the World Launch LiMo Foundation

We already have:

Maemo by Nokia (on my N770)
GPE, the GPE Palmtop Environment (running on my old Zaurus SL5500)
OpenMoko (the phone I need to buy ASAP)
Access Linux Platform, the Palm OS stuff (not seen in the wild so far)
wxEmbedded for GTK+ (don't know anything about it)
GTK+ on framebuffer (used e.g. by d-i, the Debian installer GUI)

On one hand, this looks like a success story for embedded GTK+, but I'm worried that things divert too much. Maybe LiMo comes to the rescue, but none of the forementioned companies/communities are part of LiMo. Opinions?

(Log in to post comments)

Embedded GTK+ fragmented?

Posted Jan 26, 2007 19:02 UTC (Fri) by sepreece (subscriber, #19270) [Link]

LiMO has not been open to additional members until now. They will be recruiting additional participants. It's way too early to say how many will join in. It's way too early to know whether [the big one] more carriers will sign on. The goal is reasonable - to have a consistent middleware/framework/API base for developers to build on...

Embedded GTK+ fragmented?

Posted Jan 26, 2007 20:21 UTC (Fri) by oak (guest, #2786) [Link]

I don't think Gtk fragmentation is a problem. Anybody sane
is going to merge with upstream as well/fast as they can
(if one is not going to keep very compatible to Gtk, what
was the point in taking Gtk in the first place?).

On your list wxWidgets is (on Linux) just a wrapper for Gtk,
Gtk on framebuffer is just a framebuffer Gdk backend for Gtk
(similar to the X, Windows and Directfb backends for Gtk).

Or were you talking about the stuff around and above Gtk?
The profiliteration of mobile platforms and their non-standard
APIs could be a bit of a problem...