View Single Post
Jaffa's Avatar
Posts: 2,535 | Thanked: 6,681 times | Joined on Mar 2008 @ UK
#8
Originally Posted by qgil View Post
I- You now get a UI framework based on Qt.
- The API is also Qt based. GTK+ and Clutter APIs available but not in the driver seat anymore.
- A Web Runtime maintained by Nokia will land as well.
- The 'pocketable' form factor and 'finger friendly' use cases go from 'basically futuristic' to 'big part of the deal'.
- You just happen to be in a platform that supports ARM as well, opening the door right now to the "mobile phone" crew.
- More to come when the MeeGo architecture is explained in detail.
Indeed.

There hasn't been any source code "released" so far.
There was stuff under http://repo.meego.com/trunk/repo/ - however this now seems to have moved somewhere else or been removed.

Indeed, what you have seen is a provisional post-Moblin configuration. Please wait for a first release (or at least a detailed platform description) to judge the MeeGo stack. Please also wait for the day there is an ARM configuration as well.
Yes, so the fact there's a Moblin-derived configuration shows that Moblin is providing the base of the technology, doesn't it?

About developers, Moblin developers already worked in the public so for them the change is big but still they were already working and discussing outside. Most MeeGo developers from Nokia (Harmattam developers, if you know what I mean) are still working inside Nokia, in many cases on components of the MeeGo architecture that haven't been announced publicly. I guess everything will be much easier for them once the Harmattan alpha release is out (working to release on 1Q, as promised).
Cool, hopefully that will sort things out.

Still, the amount of Nokia and Intel developers that have shown up visibly in MeeGo is very small compared to the real size of both teams. Also no wonder, there hasn't been too much to discuss for the majority of them, unless you want to be the NNth person engaging in a deb/rpm discussion.
One of the big technical questions is whether there'll be compatibility with an upstream distro to make it easy for application developers to reuse existing packages for enabling libraries. One of the big deciding factors is whether there are large enough teams of developers to make maintaining the base packages of a distro viable - without overly impacting the user-facing deliverables or the ability for existing packages to be reused.

How many MeeGo developers are there, then? i.e. those paid to work on MeeGo. It's always been opaque with Maemo, but now that MeeGo is open, this should be able to be made more clear - although there are probably commercial interests to be protected.

The Maemo development is just probably more distributed in term of companies and email suffixes than Moblin development.
True.
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
 

The Following User Says Thank You to Jaffa For This Useful Post: