Pardon. No gtk in it? http://meego.com/developers/meego-architecture
I see gtk and friends listed in middleware. And the available meego 1.0 live images for netbooks still depend on gtk heavily do they not? It's only the other targets like the handset target that is qt based.
No matter. Even if it moves completely to Qt and uses the same infrastructure that underpins KDE's netbook interface its still a _differentiated_ UI purpose built for consumer device targets. So the point I'm trying to make is still valid. Meego like Moblin and Maemo before it are all purpose built differentiated UIs that leverage technologies that are shared with other interface concepts.
The fact that Meego envisions jumping toolkits is immaterial to the market forces driving differentiated UI in consumer devices. Though I will say its interesting that no one in the laypress..even here..has really picked up on the touch framework work that meego has been slugging away at quietly leveraging qt. My understanding is the meego handset and in-vehicle 1.0 releases both make use of the meego touch framework. It would be interesting to see a well written comparison between meego's touch framework and the framework that Canonical put together.