Re: [Council] State of Maemo, Q32010.2
 

Let me be more clear: if a Qt based popular and established community project like Amarok is planning/working on going mobile (they are) then a possibility for developers willing to have a great free media player for Maemo 5 is to get in touch and exchange expertise areas. Using Qt/Mobility/Quick on 4.7 the chances are that a lot of the effort can be recycled between Maemo, MeeGo in different UXs, KDE in different UXs and Symbian in the near future.

What do you expect me to say?

Marcin is a community contributor not related with Nokia that decided to WONTFIX his own bug.

Instinctiv is a small software company that (afaik) asked Forum Nokia for advice on where to put the constrained resources they had put in their Maemo releases. Forum Nokia explained what are the perspectives of further sales of Maemo devices compared to Symbian devices, and recommended them to focus now in Qt for Symbian as primary platform in order to maximize the return of investment. This makes business sense in the times of the N8, E7, etc. Any serious developer here being asked by someone having to pay salaries of other developers would have probably answered the same.

Re: [Council] State of Maemo, Q32010.2
 

Hi Qgil / any one from NOKIA,

i am sorry if this is off topic ....... i very curious to know answers for these questions.

I am not a developer and i am just an end user. we are seeing NOKIA releases so many new apps and games for all version of symbian . why they don't even consider Maemo / N900 atleat for few apps where that could be really useful. can't they just backport few of the good apps for the N900 for the amount thry sold this device.

I see the term QT allover in nokia world which could bring apps for all of NOKIA's platform ....but in reality there is nothing for Maemo from NOKIA.

don't we deserve an answer from NOKIA why they don't care for this device?

what happened to OVI maps for N900? they could atleat give an updated map data, it was still 2002 maps data. no other company ignores their own product like NOKIA does.

i do not know how they expect more sales for N8 as no one knows when they will abaondon that too.?this is an frustration from just an ordinary user..... this phone just lives because of some great people from this community who still supports ...

Re: [Council] State of Maemo, Q32010.2
 

Ridiculous, specious argument. If that were the case they'd have opened the damn calendar source in 2009. We don't need this ex post facto crap about why Nokia dropped the ball this time (and the time before that), we need some kind of assurance that Nokia is going to break this half-opened/immediately-abandoned habit it's developing. We're all tired of getting burned.

The framework in question, which the Nokia software strategy (as though this is an entity that can have interests) has lost interest in, is one year old. One year. It was developed behind closed doors, where Nokia had a head start. What possible reason would anyone have to develop for the next big deal? So Nokia can call people like the Instinctiv devs and tell them to get bent and please quit attracting attention to this device we charged $600 for?

The n900 hasn't even been around one day for every megabyte of the SDK. And already we're being told to get stuffed. I'm going to need some serious displays of commitment to any product at all before I'm doing one more lick of work on any stupid Future Magic that Nokia claims is in the works. Meanwhile, the difference between Meego and Maemo is that Maemo is present and it works.

Meego (handset) is a tremendous joke, and I know where the n900 Meego port is going: the same direction as Mer. If you're trying to stuff the platform, well done.


Great. Let's start from scratch. That way by the time a project matures, we can scrap it all and start over when some other internal political clown car gets the pole position. Nokia's going to have to learn to make decisions and stick with them. I know I'm angry that Maemo users (and especially developers) keep getting screwed, but I can only imagine how terrible the Symbian Foundation people must feel.

Of course you don't. You've been taken into the fold. To you, the fact that Qt was cobbled in after-the-fact to our Gtk-based interface *has* to seem cool. If it didn't, you'd be out of a job.

Re: [Council] State of Maemo, Q32010.2
 

Please refrain from attacking or insulting individuals.

Re: [Council] State of Maemo, Q32010.2
 

Individuals should refrain from behaving in a way whose description constitutes an insult.

Re: [Council] State of Maemo, Q32010.2
 

Ok, so that is useful information. Out of interest, what about the Meego reference media players, are they not considered worth using/working on?

Looking at Amarok, I see that they are not overly keen on GStreamer (which is no surprise really), which makes me wonder whether it will be possible to integrate the existing DSP tasks (for video of course) with whatever backend the Qt Phonon abstraction decides to use. I'll have to do some research.

I'm quite looking forward to having a workable Meego image on my N900, and then being able to tweak/hack/add features to my heart's content. Some sort of guidance as to which apps are recommended (given the nod by Nokia ;)), etc., would be useful to avoid wasted effort - I remember this from the days of OpenZaurus where there were myriad media players, etc.

My ideal of a Meego image that I can use and still improve may not suit other people though, as we'll effectively go to something that is less polished and almost invariably will have more application bugs than we currently have in Maemo - I like this, gives me something to do, things to improve, but I fear that a lot of people will want to skip this step and remain with Maemo until Meego becomes polished enough. These people will still want bug fixes in the existing Maemo codebase.

Re: [Council] State of Maemo, Q32010.2
 

The engine is open, the rest is an exercise left to the reader ;-)

Re: [Council] State of Maemo, Q32010.2
 

These are all valid points. And I wish this projects great success, not
for maemo, not for meego or nokia, just because I prefer open developed alternatives.
But this raises the question:
Why nokia can not adopt this for its own products?

In my opinion, developing and producing an open OS based, open
community supported device and deliver it with closed source application
is a big mistake.
It was a mistake for the Nokia 770, N800, N810 and N900.

I don't say I expect to get all software for free or open. I don't say
we deserve to get this closed parts open. But I think it was a mistake
and hoped nokia could correct this.

I follow the meego handset UX development and asked for the
application specifications, I hoped the community could help to
not repeat nokias Maemo5 mistakes (missing functions in applications,
like contacts, phone-ui, calendar ...)
This was before I realised the first "meego" device won't use meego handset UX,
but instead nokias applications are developed behind closed doors again.

There is so much power in this community. Honestly, I don't see
any advantage in developing again those applications as closed source components.
Nicolai

Re: [Council] State of Maemo, Q32010.2
 

Yeah, it was a mistake and it was a big one. Although I'm sure they had their reasons. (With which I'm not familiar.)

At least now we have open source versions of these applications. There are various reference applications in the Handset UX which look promising.

Re: [Council] State of Maemo, Q32010.2
 

So where is all Qt and multiplatform porting between symbian/maemo/meego thing? u and nokia always said its chance to devs, cause they can easily port app from one os to other, and now u say it's better to dev for symbian phone? so it'a all just adv? and this is support i'm talikng about, when nokia says to devs not to develop for their own os =) now how maemo is gonna survive? or u want community to write all applications like thousands of apps for android?