why MeeGo?
 

I have had MeeGo on my netbook for a couple of weeks now, and there are some things I just don't get. I thought MeeGo was some kind of unification of netbooks and mobile devices shearing a common linux core an a GUI based around Qt. Guess what. MeeGo for netbooks has no Qt what so ever. There is nothing in the GUI that is based on Qt. It has Qt bundled, but so does every other linux distro, not to mention KDE based WMs that is all Qt.

So what was the point of MeeGo? Chrome OS will be out soon, and so will its fully open source sibling Chromium OS. For a netbook I would like a full fledges OS like the Ubuntu NR or a web based super light thing like the Chromium, preferably both. Why would I care for MeeGo when not a single thing in the GUI will be interchangable with the phone version? confuised.

Re: why MeeGo?
 

The first version of MeeGo has Clutter/MX UI. It was too soon to change the entire interface. 1.1 in 6 months will be more QT based.

Re: why MeeGo?
 

And why is that better than previuos ones? ;)

Re: why MeeGo?
 

Too soon to change the entire interface, OK, that is understandable, but as it is there is not a single byte of Qt in there. It is a Moblin 100 percent.

Re: why MeeGo?
 

Are you expecting the UX to be the same across devices?

The goal is to run the same apps, if i'm not mistaken

Re: why MeeGo?
 

But using Qt would be a large part of achieving that goal. What I think bsving is refering to is the lack of Qt and what he expects is just Moblin, and therefore wondering what the point of the whole MeeGo and convergence ideal is. I mean if that's the backbone of the MeeGo project, shouldn't it be there at the start?

I have no idea of the roadmap of MeeGo and haven't tried it out, I have no idea how much if any Qt is in it at all. Personally I'll decide on whether to use MeeGo by what services is offers me and what I can do with it, Im not particularly worried if I can run the same apps on my phone through to my desktop through to my TV....

Re: why MeeGo?
 

So what's the deal? MX is not bad - it is Clutter based, can be styled with CSS and is rather fast. There is a build of MX-1.0 in Maemo 5 extras-devel currently and the Clutter/MX demo I did compiles and runs on Maemo 5 and on MeeGo netbook. More development choices = more development. How that can be bad?

Re: why MeeGo?
 

It's using GObject - OH NOEZ! RUN! :rolleyes:

Re: why MeeGo?
 

It is bad because Nokia has abandoned Maemo because of it. Besides, more development choices also means more fragmentation, and not necessarily real world progress.

Re: why MeeGo?
 

Have you tried dual booting Maemo 5 with Android (aka NITdroid). Seemingly it is progressing faster than MeeGo :D

There is now working wi-fi and sound. Other features are yet to come. Thanks to DJ_Steve and other curious minds...