Post a Comment
Me go MeeGo, No Go, Yo!
Here is the link corrected:
http://meego.com/community/blogs/imad/2010/meego-v1.0-core-software...
MeeGo is not really targeting desktop. Think of it as "real linux" version of Android and you are on the right ballpark.
That's why I put some quotation marks around. I don't had a word for "computers targeting anyone and his dog" except "desktop", which is sadly a poor choice as you pointed out.
Intel want to put Meego on that whole kind of computers, from netbook to TVs, according to their videos. Wouldn't the desktop as a family computer become a target for them someday ?
Edited 2010-05-26 20:58 UTC
Of course it will run - but desktop market is not what's interesting for Nokia or Intel in MeeGo development.
It's more of a desktop OS than Chrome OS but less than, say, Ubuntu.
It would, but Linux people tend to expect Gnome/KDE like experience (optimized for mouse, full keyboard + large non-touch screen).
Pulseaudio is essential for those who want a future where linux -- as windows and osx -- have a sound system which just work without hassle.
On my hardware it's impossible to adjust the volume only using alsa. (HDMI sound).
I use, skype, I have usb headset, I listen to music and sometimes visit web sites that have flash videos with sound. Using all this in an accpetable way involve having a system like pulseaudio.
PS. I'm not implying pulseaudio is flawless, just pointing out that it's the right way forward. At least for me, it's a great leap forward.
Edited 2010-05-26 22:27 UTC
Stabilization without introduction is idealistic but not practical with the current model. Things that work well in a test environment even with a large QA team would have problems in the real world due to the enormous amount of variations in hardware for something as fundamental as a sound system. It is impossible that progress in such cases will be linear.
Every single change in potentially disruptive and free software development is based on rapid releases and quick iterations to gain maturity over time. That doesn't mean that things cannot be improved. For ex: more test cases can help.
It just can't, never, ever. It's impossible. The code is GPL, which mean the product will always be free as in free speech. Lock in is impossible. Undocumented standard is impossible. Becoming Microsoft is impossible.
Right, products are what will make this interesting. MeeGo is not being pushed to normal people at this time; technically not even application developers.
What's not going so well for N900? PR1.2 just got released, and it's "opening the floodgates" for commercial (Qt) development for the platform.
This is incorrect. The stuff you have seen is current iteration of "Netbook UX" (user experience) for MeeGo, which is indeed basically new Moblin.
The Handset UX will be released at a later date.
This is incorrect. The stuff you have seen is current iteration of "Netbook UX" (user experience) for MeeGo, which is indeed basically new Moblin.
The Handset UX will be released at a later date.
But don't you think that having just a single code base (let's call it: Core UX) implemented on Qt would have done their lives easier? and the specific things for netbooks and phones coming on top of that? Having two or more "personalities" on top of the core OS will be a headache.
Ok, I don't have any technical knowledge on Meego/Maemo/Moblin so I'm just speculating here.
But don't you think that having just a single code base (let's call it: Core UX) implemented on Qt would have done their lives easier?
Not really at this timeframe.
It would make the life easier if it was there already, but these people have products to deliver and deadlines to meet - and code that exist already.
The important thing is that application developers have a consistent api to develop against. Whether the window manager is coded with xlib or turtles does not make or break the platform, even thought in the long run maintenance of consistent system is cheaper.
This recent thread may be of interest to you:
http://lists.meego.com/pipermail/meego-dev/2010-May/002607.html
So what happened to Maemo in this 'merger'?
I've not tried it yet but the screenshots and text are telling me that this is basically an updated moblin w/ chrome and social networking tagged on? What has been took/ developed from Maemo here?
I've not had funs to get one but I was quite excited after having a go with Maemo 5 on the N900 and I was looking forward to how that would progress but it seems Maemo 5 could be its last major version- assassinated by 'super moblin'.
I'm sure I'd heard recently that Meego was not to be ported to the N900 but now it seems it is. I was very keen on the N900 / Maemo 5+ but now I need to try this out and I'm not so sure anymore as moblin didn't impress me. Maemo 5 being based upon Debian was key to its cool.
Edited 2010-05-28 06:55 UTC
If you had read the actual announcement, you'd know that the Moblin GUI is just for MeeGo Netbook and that the MeeGo Handset GUI is not done yet and will follow in MeeGo 1.1.
Agreed, also screenshot looks not at all tuned to mobile use. It required a large screen in both directions. (thought that is 'fixable')
For me it all looks feels and for all purposes -is- Moblin. Not Maemo. Sure there working on it, but as it looks now, it has none of the cool underpinnings (debian/ubuntu), none of the gui nokia developed the last couple of years (and works very well on PR1.2), everybody has to -again- recompile there apps, even worse repackage it.
I really really hope that Nokia will release the entire Maemo codebase (the closed parts) to the community.
They wanted a community, they got it and immediately wanted a new community. (roll over to meego or die)
Then please give the ones left behind the entire thing they signed up for.
At least then we can continue making our N900 devices cool for years to come. Make decent ports to devices like the beagleboard and carputers. Fix the unmaintained packages issues and become closer/sticky to upstream debian/ubuntu sources.
Edited 2010-05-29 00:09 UTC
I just tried it on an Aspire One 110, booted off an USB stick. I certainly haven't seen such a dumbed down interface for a while. I guess it's OK for kids, teens or grandmas, but for the average user, it's just too much hand-holding. Not to mention that even though it connected via WiFi, after two minutes the connection just gave up and I couldn't even ping the router.
It took me about 3 minutes to figure out how to turn the darn thing off. The only way was the power button, since I couldn't even find a terminal to type shutdown into.
Perhaps it could be useful in conjunction with the lighter-weight KOffice 2.2 on a netbook.
Several comments on this thread have managed to put me off, however. Firstly, the only available browser seems to be Chromium. There seems to be no way to use any applications other than those in the Meego repository, and there are none of those (so no KOffice 2.2).
Hmmm.
I think I'll stick with waht I have got running now. Standard Kubuntu Lucid, with the Lancelot menu with "show categories in panel" option, (also enabled the classic menus via right-click on the desktop), and with the panel moved to the left-hand edge of the netbook screen (vertical panel). Also I have enabled several keyborad shortcuts to start common applications. This gives me a standard KDE4 environment running happily on the netbook.
This arrangement also maximises vertical screen real-estate (essential for a netbook) and it allows me to run KOffice 2.2 as the Office suite (which is ideal for a netbook since KOffice 2.2 is very functional but still lighter weight than OpenOffice, and the KOffice 2.2 UI is designed with a widescreen in mind, and consequently it has better use of vertical screen real-estate). Now all I need is to find a set of Kubuntu backport packages for KOffice 2.2.
Anybody had any luck yet with that last step?
This page seems to be saying that a port of KOffice 2.2 to the Kubuntu backports is low urgency, and that it hasn't been done yet.
http://www.ubuntuupdates.org/packages/show/202860





