The Following User Says Thank You to tswindell For This Useful Post: | ||
![]() |
2011-02-14
, 13:56
|
Posts: 163 |
Thanked: 256 times |
Joined on May 2010
|
#12
|
![]() |
2011-02-14
, 14:14
|
|
Posts: 1,062 |
Thanked: 961 times |
Joined on May 2010
@ Boston, MA
|
#13
|
![]() |
2011-02-14
, 14:18
|
Posts: 376 |
Thanked: 511 times |
Joined on Aug 2009
@ Greece
|
#14
|
I don't know where the impression is coming from that Intel is the only one working on Meego now. Nokia specifically said that Meego will continue as a project geared towards future disruptions in the smartphone market (i.e. Maemo). Whether it gets the attention it needs and deserves has yet to be seen but Nokia has not dropped out of Meego altogether.
![]() |
2011-02-14
, 14:22
|
Posts: 163 |
Thanked: 256 times |
Joined on May 2010
|
#15
|
I don't know where the impression is coming from that Intel is the only one working on Meego now. Nokia specifically said that Meego will continue as a project geared towards future disruptions in the smartphone market (i.e. Maemo). Whether it gets the attention it needs and deserves has yet to be seen but Nokia has not dropped out of Meego altogether.
![]() |
2011-02-14
, 14:24
|
Posts: 163 |
Thanked: 256 times |
Joined on May 2010
|
#16
|
MeeGo is tied to Qt and Qt's future is in risk. Surely KDE can fork Qt but this won't help. One of Qt's big advantages is that it's cross-platform, but an opensource project most probably won't continue that. People from KDE may improve Qt but this will be done mostly with Linux in mind.
Of course Qt may become something like the Linux kernel wheren OS vendors may jump in and add support for their OS, but i seriously doubt that.
![]() |
2011-02-14
, 14:25
|
|
Posts: 1,309 |
Thanked: 1,187 times |
Joined on Nov 2008
|
#17
|
![]() |
2011-02-14
, 14:26
|
|
Posts: 1,309 |
Thanked: 1,187 times |
Joined on Nov 2008
|
#18
|
![]() |
2011-02-14
, 14:28
|
Posts: 724 |
Thanked: 1,255 times |
Joined on Nov 2007
@ Cambridge, UK
|
#19
|
Come on, please!
Translated from scumbag double-speak language that means:
"We will drop MeeGo like a turd down a toilet as soon as our previous agreements with Intel make it possible to do so".
Which means that Nokia will release the one MeeGo device that's currently in development, and right after that will fire all of their MeeGo developers, never to release another MeeGo device again.
![]() |
2011-02-14
, 14:28
|
|
Posts: 4,384 |
Thanked: 5,524 times |
Joined on Jul 2007
@ ˙ǝɹǝɥʍou
|
#20
|
![]() |
Tags |
its just a fail, stop dreaming, windelnkiabumby |
Thread Tools | |
|
The handsets that will eventually be released, based on MeeGo will probably be extremely different UXs to those you've already seen screenshots of from the meego.com handset UX. The "desktop" UX is likely to be radically different for each manufacturer, Nokia included. The important parts of the platform are the underlying APIs and systems and Qt. So we can write one and deploy on _any_ MeeGo device.
What I invisage is a Nokia handset this year, running _their_ MeeGo and maybe other handsets running the vendors MeeGo. The stock apps and current handset UX are cool if you want to remove any kind of vendor branding and support a fully open platform. But that is unlikely to be where normal users will be, but we can still develop OSS that runs on anything, thanks to the common platform APIs and Qt.