On Thu, Feb 3, 2011 at 10:38 AM, Claudio Saavedra <[email protected]> wrote: > On Sun, 2011-01-30 at 16:19 +0100, Dave Neary wrote: >> Hi, >> >> Niels Mayer wrote: >> > Just curious at what level this is being "ported" or "integrated" -- X >> > windows, OpenGL ES, or both? >> > >> > ............... >> > http://blogs.gnome.org/foundation/2011/01/17/gtk-meego-handset-bidders-selected/ >> >> As far as I know, the goal is to ensure that upstream GTK+ works well >> for MeeGo, so that Hildon and Maemo application developers (for example) >> can simply recompile their applications for MeeGo. Currently there are >> some differences between upstream GTK+ and Maemo 5 GTK+ which make it >> impossible to just bring in Hildon as a dependency and recompile (or >> even, ideally, not need to bring in Hildon, because all the useful stuff >> will be integrated upstream, and Hildon will become an API compat layer). > > > You are stretching a bit your imagination with all this, but you are in > the right direction. Right now, we are focused in two things: 1) getting > the most interesting stuff from Hildon and Maemo-GTK+ in upstream GTK+, > and 2) Getting all the necessary glue for GTK+ apps to work in the MeeGo > Handset (like the IM and WM support, for instance). > > Whether Hildon can be a compatibility layer or not, that's to be seen. > Don't forget that we are working with GTK+ 3 in mind (yes, we are), and > being so, you can't just recompile. You'll need to port anyway.
So does the work include moving the netbook related UX to gtk3 too? Peter _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
