<br><br><div class="gmail_quote">On Fri, May 6, 2011 at 8:36 AM, Ville M. Vainio <span dir="ltr"><<a href="mailto:vivainio@gmail.com">vivainio@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Fri, May 6, 2011 at 3:24 PM, Sunny B <<a href="mailto:sunnyb7532@gmail.com">sunnyb7532@gmail.com</a>> wrote:<br>
<br>
> 1) Clarification of the SW Architecture - Is it Meego Core OS with a Nokia<br>
> custom UI or UX on top? QGil has said MeeGo APIs, but now Dave Neary says<br>
> some legacy Maemo APIs (in addition?).<br>
<br>
</div>Harmattan is evolution of maemo5, with no MeeGo Core lineage. It has<br>
several components that are shared with MeeGo though. That's why it's<br>
said to be "meego compatible".<br>
<br>
> 3) MeeGo compliance<br>
<br>
Harmattan is not MeeGo compliant at all, starting with the fact that<br>
it's using deb instead of rpm.<br>
<div class="im"><br>
> 5) To what extent will developers of Maemo5 and Maemo 4.1 apps be<br>
> comfortable with Harmattan and find it a "natural" extension.<br>
<br>
</div>Back-end stuff will feel very familiar, GUI development is supposed to<br>
be done in QML (familiarity of which can be argued, as it's an overall<br>
new phenomenon).<br>
<div class="im"><br>
<br>
> I agree with Andrew that the thing is a mess. I think that's beyond the<br>
> control of <a href="http://maemo.org" target="_blank">maemo.org</a>. Perhaps we can try to clarify things through<br>
> discussions with MeeGo people - core Meego OS goes to <a href="http://meego.com" target="_blank">meego.com</a> and<br>
> Harmattan UI and UX are with <a href="http://maemo.org" target="_blank">maemo.org</a> or something more strained than<br>
> that. But the division is admittedly not good - we'll have to see. I hope<br>
> we get some clarity at the conference.<br>
<br>
</div>As said there is no "Core MeeGo OS" in Harmattan.<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div><br>Thanks Ville. As to MeeGo compliance, I guess I meant that in a larger sense, not the certification program, but I didn't know the core OS wasn't MeeGo. The extent of shared lineage I hope some more knowledgeable than I can address in due course. I know QGil is still trying to get the device "accepted" in MeeGo community and his session was not accepted at Conference. It seems poor Harmattan may be the poor child born after its parents divorced.<br>
<br>Can 2) and 4) be answered sometime before device release? Although I understand if the Nokia UX/UI cannot be known until the big reveal. <br></div></div><br>