maemo.org - Talk - The EPIC N9 anticipation thread

maemo.org - Talk (https://talk.maemo.org/index.php)

- Nokia N9 / N950 (https://talk.maemo.org/forumdisplay.php?f=51)

- - The EPIC N9 anticipation thread (https://talk.maemo.org/showthread.php?t=72977)

Re: N9 hits FCC???

Quote:

Originally Posted by mece (Post 1006878)

@mikecomputing Ville Vainio said, and I quote, "Harmattan is not MeeGo compliant at all" so I gather it's just that. not compliant.

I posted the link to the mailinglist stuff in this thread already. Here.

MythBuntu is also not Ubuntu compliant(I think). But it has an easy migrator which can migrate ubuntu apps with a simple process.

EDIT:Also you said that this device will be announced in May 17th at the nokia conference. Then I should say we are also close to the MS Tech Ed :p

Re: N9 hits FCC???

this thread is way off topic..

Re: N9 hits FCC???

...MeeGo? ...Maemo? ...Harmattan? ...MeeGo 1.x / Maemo 6?

****! Who cares!? :mad:

The differences doesn't matter that much. It's Linux!
And thanks god not Windows Phone... so please, stay together and stop this discussion. It's the N900 successor. And a step more in the MeeGo direction. The step 5 of 5.
There are enought similarities. And it should be more open than WebOS. Open the Shell and take over the system until it fits your needs. Period.

Re: N9 hits FCC???

Quote:

Originally Posted by mikecomputing (Post 1006884)

Hmm okay does this Ville working on Nokia? I mean does he have fully info whats not compliant? Etc..

Would be intresting to know this. Hopefully Nokia will clarify whats not on conference.

Yes and yes. Once someone has the device all will become clear :) can't wait!

Re: N9 hits FCC???

Quote:

Originally Posted by tswindell (Post 1006886)

Urm, what? If the MeeGo project says MeeGo UX (Components) is required to be compliant, then yes, it is required to be compliant.

What I meant was none of those UI is yet decided. Means not added to compliance list.

Quote:

Harmattan is not MeeGo compliant, Nokia know this, MeeGo community know this, and you should accept that. Now, Nokia want a waiver from the MeeGo project to (falsely imo) have permission to state that Harmattan is MeeGo compliant, it isn't we all know this but Nokia are arguing that it's acceptible in this case, because they both have compatible Qt APIs which is where most developers will live.

You may have a pointe but would be intresting too know what is not compliant at the end. None of us really know. But it seems to mee you and many others takes your own conclussions on facts that was 2009 when we all knows things has changed since then.

Example: BusyBox instead of Bash. again I dont see any reason they used BBox its 2011 now not 2009. I guess even Android is using full bash/corelibs now.

I also rtemember Nokia and Intel was talking about systemd.

But to me it looks like the community sometime "want" Nokia to break compliance. Just give an example the decision to go EvolutionDataServer instead of tracker. Intresting was this change was announced some weeks after 11 february.... Wtf? I mean how the hell would Nokia have a chance to integrate this its soon tyo be released device? I am sure this would have been discussed alot more before they did this decions if it had'nt been because of Mr Elop...

Quote:

Using DUI wouldn't break compliance. Why would Nokia use DUI? Because Harmattan, for the last f'ing four years has had DUI. That was the whole point, Harmattan step 5/5, DUI replacing Hildon.

Yes true but stuff has changed since then. QtQuick was introduces as main API and they may dish it DUI totally. Reason: They already said in sept that libmeegotouch(= DUI) was deprecated.

DUI git here:

http://qt.gitorious.org/maemo-6-ui-framework wish then was:

renamed to libmeegotouch(now deprecated but still some OSS devs playing with it):

http://meego.gitorious.org/meegotouch/libmeegotouch

libmeegotouch deprecated in favour of

http://qt.gitorious.org/qt-components/qt-components

But is there is no meego based commits for month by Nokia. Kate said it will soon be released public on meego mailinglists. I take that as qt-componets is the main UI also on Harmattan! not some wierd old "DUI"

Quote:

Especially Nokia? Are you ******ed? Qt Components is being developed in the open, it was MeeGo UX that was behind closed doors, both are open now.

See above...

Re: N9 hits FCC???

Quote:

Originally Posted by tswindell (Post 1006890)

Why? Why is this so important to you? and if it is so important why don't you read the bloody compliance doc instead of gesticulating your own guesses and opinions (which have mostly been rubbish) ...

Intresting you saying "guessing" well I can say exatly the same too you! We have to wait and see.

End of this pointless discussion.

Re: N9 hits FCC???

Quote:

Originally Posted by mikecomputing (Post 1006944)

Intresting you saying "guessing" well I can say exatly the same too you! We have to wait and see.

End of this pointless discussion.

You could say the same, but unless stated otherwise everything I've said has been based on real information that has either come out in direct conversations I've been involved with or publically discussed. Yours seem to be out of thin air ...

Re: N9 hits FCC???

Really, the only thing that matters is easy interoperability of software between OSs. If it has that, it doesn't matter what is under the hood.

Re: N9 hits FCC???

Quote:

Originally Posted by gerbick (Post 1006832)

This is great information; however it (to a pessimist) signals how isolated Harmattan will ultimately be in regards to the MeeGo ecosystem/code base.

That's enough of an difference to render some apps a probably one release (like Skype) or worse... vendors will be forced to split their dev teams and Harmattan will only get niche level support, if that.

Good information to know though.

I used to worry about the Meego vs Harmattan debacle in the same way.
Not any longer. And the main reason is that I've found Meego _itself_ to be even more inconsistent.

Meego on the days we started to know what the Harmattan stack would look like is at least as different from today's Meego stack as those days' Harmattan stack was. At this point, I'm willing to say that the entire DEB vs RPM difference is a minimal nuisance when it is at stake even the way applications will be spawned.

So I bet Harmattan is an example of the Meego-ish things that will come instead of the outdated mess many people believe it to be.

Either way. There is clearly a plan to deal with all of the Meego inconsistencies between platforms which is to do the core logic once and implement one UI per platform.

And us slightly lower-level guys where already pretty much tied to the Harmattan way of life whatever Meego came up to be, so no worries either...