Linked by David Adams on Tue 28th Sep 2010 21:58 UTC
Fedora Core The Fedora 14 Beta was released today, but as a Network World article points out, it "will be the first Red Hat supported distribution to let users choose MeeGo as their desktop." This new release will also include the Sugar interface, intended for netbooks, and "will also be the first version to fully incorporate Red Hat's VDI (virtual desktop infrastructure), called SPICE, or Simple Protocol for Independent Computing Environments. SPICE will allow Fedora to host virtual desktops that can be accessed over a network."
E-mail Print r 1   · Read More · 26 Comment(s)
Thread beginning with comment 443229
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

Woah, we seem to have veered from the tablet UX to the netbook UX in your comment. Let me straighten my glasses. Ok, ready. ;-)

Intel's ecosystem for netbooks is called AppUp, which supports both Windows and Meego (and legacy Moblin). It's reasonable to assume that a different Linux distro using the Meego UX on x86 processors such as Atom would support both AppUp and the native distro repository, similar to how Ubuntu has for years supported both Universe and the (not terribly well-known) click-n-run warehouse.

Back to touch apps - smartphones and tablets generally get their apps from the operating system's app store, so for Meego that's probably Nokia's Ovi store. A tablet running (say) Ubuntu with Meego UX would probably support both Ovi and Universe, just as Maemo on N900 supports both Ovi and the native Maemo repository.

In both cases, though, Meego is far more open than iOS or even Android. You can load any apps you want from any source. App stores and repositories just make it much simpler for "normal" people. :-)

Reply Parent Score: 2

Radio Member since:

Yeah, sorry for the mix between netbook and tablet (although their share the same problem : everything needs to have big UI elements, for netbooks to be readable, for tablets to be touchable).

But those apps rely on libraries and API; won't there be a widening gap between MeeGo-pure, and MeeGo-on-top-of-SUSE-or-Fedora? If, next year, PulseAudio is replaced by a new sound API (just an example, could be anything else - replaced by Wayland, or something I can't think about, any of the hundreds of libs), Fedora will certainly switch to it, bleeding-edge as it is, OpenSuse will follow a little later, but how would the AppUp/Ovi apps deal with it?

Edited 2010-09-30 21:35 UTC

Reply Parent Score: 1

ricegf Member since:

Good question. I'm not enough of an authority to know for certain, although my understanding to date is that QT4 abstracts the underlying systems. So when writing Meego apps, you don't write to PulseAudio or Wayland or (shudder) - you write to QT4, period.

That's how QT4 apps run on Windows, Macs, desktop Linux, WinMo 6.5, Meego, Maemo and Symbian with basically a recompile. Abstraction.

I'm not claiming that you won't want to make *any* code changes, you understand - a desktop QT4 app won't "feel" right on a Meego tablet. Just saying that your concern about "hundreds of libs" being unique depending on which platform hosts the Meego UX's, and requiring significant code rework to make them compatible with each Meego instance, is probably off-base. Probably. And given (say) several Atom-based netbooks running Red Hat with Meego, Suse with Meego, and Intel's Meego, binary Meego apps should run just fine on all three just like Gnome apps or KDE apps run unmodified on Red Hat, Suse and Ubuntu for x86 today.

But we'll know once we have several distinct Meego products in the market, won't we? ;-)

Reply Parent Score: 2