![]() |
Re: MeeGo's Community Woes
From the article:
"Apparently Nokia is also having problems with its traditional developer base as well — the devs are tired of waiting for devices and the OS to be done, already. This is not a slow-moving market." I dont get why some people is not get it! I mean alot of SDK in meego is also working on N900 from scratch! We have QtQuick/Qt/QtComponents directly in Maemo5 we can develop apps working both for Symbian/Maemo and Meego using QT. So start develop instead of whine IMHO. Releasing some halfdone Meego hardware now would just kill Meegoproject. |
Re: MeeGo's Community Woes
Quote:
|
Re: MeeGo's Community Woes
Quote:
Also alot of the whining is old. Those who had read the meego compliance specs and the stuff about trademark should understand that this rules are there to not make Meego being as fragmented as in the case of Android. However I could agree with some of his statements. There need to be better communication to the oss developers. |
Re: MeeGo's Community Woes
Quote:
|
Re: MeeGo's Community Woes
Quote:
You have to get Meego devices out first before you get the developers interested in working on them. Granted QTQuick allows developers to write a computer application and bring it over to Meego. There are still alot of companies interested in Meego, I'm just wondering how long they'll stick around as Android continues to grow. The longer they give Android to grow, the bigger the battle Meego will have to face. |
Re: MeeGo's Community Woes
Why does people use the word 'Bricking' for everything from 'contacts not syncing' to 'usb socket snapped'
IMO N900 is unbrickable in any case! |
Re: MeeGo's Community Woes
Maybe MeeGo is actually quite completed and devices are being made as we speak. Nokia and Intel perhaps want to release MeeGo when its fully completed and ready to compete against the big boys.
Imagine, Intel releases a netbook (like Google did with the CR-48) at the same time; Nokia releases a smartphone (as good as the iPhone 4 and EPIC 4G's), at the same time MeeGo releases its sources (FINAL, non beta). I feel like if this was done in September 2010, then the devices got updates and were improved and source was improved, then newer netbooks (ASUS, Acer etc), new MeeGo smartphones (Nokia etc), and Tegra2 tablets were delivered in December. The holiday season would mean MeeGo would have a healthy start, probably get the jump on WP7, WebOS and RIM. All it would need is continual improvements without fragmentation, some time to bake, then it could've been the top 3 choice; after iOS and Android. |
Re: MeeGo's Community Woes
The funny thing is that MeeGo seems to be running better on the Archos 5 tablet
Compared to MeeGo on the N900 it's highly embarrassing for Nokia. There are still problems with charging the battery via the wall charger under MeeGo on the N900 and performance issues with the video driver is also a problem. It just seems Nokia's lack of will to get MeeGo working properly on the N900 is stifling the project. After all this time there are still issues charging the N900 and you still cannot make phone calls under MeeGo. These should have been priorities and Nokia should have ensured basic stuff like this was quickly working. Its a shame because there are many developers working hard as they can to get MeeGo ready but are hamstrung by Nokia's "closed-mind, closed source" attitude. |
Re: MeeGo's Community Woes
Quote:
Do I really need to pull out http://www.youtube.com/watch?v=cWtML...layer_embedded all the time? Archos port is basically Handset UX on top of GLES drivers and that's it. |
Re: MeeGo's Community Woes
Is there a "N900 MeeGo Status" page listing what's working and not working with MeeGo?
Or something like a "Milestone Page" showing what is completed and still outstanding? |
All times are GMT. The time now is 08:02. |
vBulletin® Version 3.8.8