“Today we are announcing the project release of MeeGo v1.0. This release provides developers with a stable core foundation for application development and a rich user experience for Netbooks. The MeeGo Netbook user experience is the first to appear, with the development of the MeeGo Handset user experience moving to the open in June.”
I wonder if it works on my Macbook …
Me go MeeGo, No Go, Yo!
Here is the link corrected:
http://meego.com/community/blogs/imad/2010/meego-v1.0-core-software…
…with the overhyped “social networking” crap polluting the desktop as a reason for *not installing* it.
It’s backed by Intel and Nokia, though, so it might succeed. Just hope that it won’t end up completely dominating the “desktop” linux distribution world and become another Microsoft in that area. We already rely too much on Intel in the computer world…
Edited 2010-05-26 20:23 UTC
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).
Sorry for the edit. Thought you did not see it yet.
Your point makes sense. Though linux users have proven to accept (unneeded and painful) breakthrough changes like the introduction of PulseAudio in the long run. Wait and see…
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
Well, you make a point, but it does not excuse introduction of a half-baked soft in all linux distros. A simple ALSA patch should do the trick. And if pulse is really needed (which I heavily doubt), then it should be stabilized before introduction.
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.
Well… Actually, Pulse’s problem is fairly simple AFAIK : it does not grab the right output among the available alsa channels, and does not provide the option to use another one, though it sounds available in the GUI.
Question is : why can just about every single piece of software except pulseaudio find out how to use the right output channel ?
That’s hardly the right question. The right question would be, where is your bug report? 🙂 Note that a lot of the details here are hardware specific so inviting generic commentary is not useful
Do you think that a bug report based solely on GUI symptoms could be of any help ? I don’t know enough about PA’s logging mechanisms and internals in order to technically describe what’s wrong, except by “no analog output channel available on an Envy24 soundcard that’s perfectly supported by pure ALSA”.
I think that the problem could be of the following nature : main output not called “PCM out” + lame hardware detection that trashes everything that does not bear that name = no output. However, I don’t know how PA internally works, so I can’t say for sure that PA devs have been nearsighted enough to hardcode an output channel name that’s heavily hardware dependent…
On pure ALSA, you simply adress the “no sound” incident by opening alsamixer and turning the volume of the output channel (DAC 1 and DAC 2 for me) up. But on most PA-“powered” distros, alsa’s config is garbled by pulseaudio, and you can’t do that anymore.
Edited 2010-05-27 14:40 UTC
You don’t need to know the internals to file a bug report. You file it as a end user stating the symptoms you see and provide information about the hardware and any other relevant details. Then the developer or a bug triager will ask for more details if needed. PulseAudio is a layer over ALSA. It doesn’t replace it.
I can assure you that it totally trashes ALSA’s config, even though it does not replaces it. Once PA is here, you can’t even use standard alsa tools like alsamixer or alsactl to access the device’s output channel directly.
I trust you but it would be useful for you to direct a specific bug report to the developers and get it fixed.
I’m going to agree, I think that social networking crap should be an optional application. I’ll give them points for using Qt though.
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.
Who cares how immature it is, its just software which can be updated.
Lets see Intel or Nokia release a product.
The first publicly available Android device, the G1, got out there early and has seen updates. Although…. its not going so well for the N900 is it?
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.
Maybe this comment comes late, but, after reading some reviews to Meego, it seems to be an improved version of Moblin with nothing coming from the Maemo/Qt side… Is that correct?
Let’s see if Nokia will continue supporting Maemo after Maemo/Moblin marriage
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.
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
You’re completely right.
I will read the thread, thank you!!
I hope it has a better software catalog than Moblin2. It was ridiculously hard to install anything there other than the few apps available on the Moblin repositories.
Just getting decent multimedia support was a PITA.
Anyone try this in vmware fusion? I did and it doesn’t seem to work for me.
VirtualBox works neither.
Yeah, I tried that too. Apparently, you need a system sse3. Also, turning off the silent boot gave me some hints, but I forgot what the messages I saw were. Oh, well…
Somebody should port GNUstep on it. Then we have an iPhone for geeks.
I must confess that my first impression is very positive and, shame on me, it’s based only on the screenshot on the linked page.
Just like neolander, I think the “social networking” thing is just too much.
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