maemo.org - Talk
Page 5 of 5 « First 34 5
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   MeeGo / Harmattan (https://talk.maemo.org/forumdisplay.php?f=45)
-   -   Renaming "Maemo 6" to MeeGo / Harmattan (https://talk.maemo.org/showthread.php?t=44664)

droitwichgas 2010-06-11 20:26
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Reading between the lines I assume the MeeGo-Harmattan Hybrid will not be called just plain Meego as most of us assumed but something along the lines of MeaGo (I can see another lenghy " chuck norris speculation about ..." thread starting already!) However surely this will lead to more confusion amongst developers who will now have to think about developing for meamo or MeaGo or simply sit and wait for MeeGo to appear.

I appreciate QT should mean this is not an issue but since PR1.2 I haven't seen one decent game/app developed on QT released or any suggestion we are likely to see any sometime soon.

Is all the work getting a community based MeaGo going to be any real benefit to an average N900 user?

qgil 2010-06-12 07:27
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by droitwichgas (Post 711155)
this will lead to more confusion amongst developers
Are you a developer? What is exactly confusing for you now?

Even for developers the situation is now about targeting Qt / Maemo 5 and for the rest wait and see. There are not evden much details about the Web Runtime, which will bring a level of cross-compatibility that can't be compared to native programming.

droitwichgas 2010-06-12 07:55
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by qgil (Post 711674)
Are you a developer? What is exactly confusing for you now?

Even for developers the situation is now about targeting Qt / Maemo 5 and for the rest wait and see. There are not evden much details about the Web Runtime, which will bring a level of cross-compatibility that can't be compared to native programming.
No just an end user who's disappointed at the lack of any quality games/apps availablefor the phone via the Ovi store, which I am more than willing to purchase should they ever appear.

Venemo 2010-06-12 08:22
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by droitwichgas (Post 711689)
No just an end user who's disappointed
And what makes you think that developers will be confused by this?
Developers are smart people, you know.

By the way, my thoughts are:

What Quim said, basically means this:
"If you want to develop for MeeGo, start developing today for Maemo 5, and we promise that your app will run on MeeGo with a single click on a button."

That's it.
The good thing about this is that it is actually true provided you wrap your platform-specific API calls within #if-s (or don't use them at all).

qgil 2010-06-12 08:46
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
The games you are looking for probably are based on OpenGL ES, and I don't think the developers working on those games will get confused.

droitwichgas 2010-06-12 09:50
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by Venemo (Post 711705)
And what makes you think that developers will be confused by this?
Developers are smart people, you know.

By the way, my thoughts are:

What Quim said, basically means this:
"If you want to develop for MeeGo, start developing today for Maemo 5, and we promise that your app will run on MeeGo with a single click on a button."

That's it.
The good thing about this is that it is actually true provided you wrap your platform-specific API calls within #if-s (or don't use them at all).
If that is the case why is it that we are not seeing any decent games/apps for the N900, are developers simply not interested in this device/platform, if so, why is that, are Nokia not encouraging them to develope anything?

Since PR1.2 the only thing, bar Angry Birds Level 1, I have downloaded is the World Cup app but it is irratating to see that they are already advertising apparently decent games for the N8.

attila77 2010-06-12 09:53
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by Venemo (Post 711705)
What Quim said, basically means this:
"If you want to develop for MeeGo, start developing today for Maemo 5, and we promise that your app will run on MeeGo with a single click on a button."

That's it.
The good thing about this is that it is actually true provided you wrap your platform-specific API calls within #if-s (or don't use them at all).
#ifdefs don’t cut it. That was one of the reason Qt was born in the first place.

An example about the confusion stems from the many announced promising technologies which, to the developer, have time unclear future or internal relations. Whatever you do on Maemo 5 will look crappy (or out-of-place at best) on Harmattan, and there is already UI technology that points beyond Harmattan. You already have three (or four, if the reference UX counts) different ways of doing an UI without the necessary background knowledge or insight to make a stategic decision which one to use. And I haven’t even started talking about Symbian, which will certainly be a major factor in technology choices in any paid developer’s work. So no, it’s not really clear, partially due to the speed of technology development, but is worsened a lot by the incoherent naming strategy which will have to be corrected before any final release is made.

And a general comment - ’smartness’ of developers have nothing to do with it. That’s like saying Qt doesn’t need documentation - if you’re smart enough you’ll figure it out based on the source. The goal is to make the tools easily approachable and to minimize the learning curve and potential communicational errors later on. A clear structure (naming included) helps *everyone* interested in the platform.

Venemo 2010-06-12 10:06
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by attila77 (Post 711781)
#ifdefs don’t cut it. That was one of the reason Qt was born in the first place.
Qt offers platform-specific APIs for every platform.
This means that if I'd like my app to have the right look and feel for the platform, I'll need to use them.
If you want you app to run on other platforms as well, you should #ifdef them.

(Not to mention the platform-specific UI stuff that Qt has no abstraction for - in this case, direct reference to libraries of that platform are needed.)

Quote:
Whatever you do on Maemo 5 will look crappy (or out-of-place at best) on Harmattan
Why would it?
I guess QMainWindow and QPushButton and so on will look as defined in Harmattan's theme.
Of course, a little Harmattan-specific APIs here and there (with #ifdefs of course, to keep the app compiling on Maemo 5) and all is well.

And I haven't spoken about Symbian yet - if a Qt app needs to run on different versions of Symbian and on different versions of Maemo (and perhaps desktop?), and wants to maintain the best look and feel on each platform, #ifdefs are inevitable.

Quote:
You already have three (or four, if the reference UX counts) different ways of doing an UI without the necessary background knowledge or insight to make a stategic decision which one to use.
What are those different ways?
I'm asking out of curiousity, as I'm quite new to Qt.

Quote:
And a general comment - ’smartness’ of developers have nothing to do with it. That’s like saying Qt doesn’t need documentation
My point didn't have anything to do with Qt or its documentation.
My point was for a non-developer who assumed that developers would get confused.

Quote:
A clear structure (naming included) helps *everyone* interested in the platform.
As I say the n-th time here: agreed!

attila77 2010-06-12 11:38
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by Venemo (Post 711788)
Qt offers platform-specific APIs for every platform.
This means that if I'd like my app to have the right look and feel for the platform, I'll need to use them.
If you want you app to run on other platforms as well, you should #ifdef them.

Why would it?
I guess QMainWindow and QPushButton and so on will look as defined in Harmattan's theme.
Of course, a little Harmattan-specific APIs here and there (with #ifdefs of course, to keep the app compiling on Maemo 5) and all is well.

What are those different ways?
I'm asking out of curiousity, as I'm quite new to Qt.
I used to code in Qt from before the times Maemo existed. The great thing about Qt was that, in gereneal, there WAS no #ifdef required (i you had it, it was considered bad programming or platform incompatibility). Whether you coded for XP, Mac or Linux, you used the same API. It was (still is) a really cool thing. With mobile development this changed - my Maemo apps are already littered with #ifdefs as I want them to compile on my deskop, on Qt4.5 (for N8x0) and Qt4.6 (PR1.2), and chances are there will be another volley of #ifdefs for each release of Qt and each device (worse yet, every firmware release), and my Qt code starts looking as ugly as any bog-standard C++ code that is trying to be multiplatform. And that scares me as a developer, since Qt was supposed to (and did in the past) relieve me from that. And I’m not just talking widget libs here.

As for the different ways
  • the "standard widget from code" approach. This will work everywere, look fairly localized but also the one that users usually refer to as "crappy looking community apps". No whizz, no bang. Adaptation already needed due to input technologies (fingerscroll, etc). Requirements: Qt

  • QtDesigner approach - similar to above, but using the QtDesigner UI editor. Speeds up UI development by a more visual way of assembling components. The downside is that QtDesigner does not know anything about mobile use, so you are missing out not only on the mobile-specific widgets, but also the generic look and styling - you do not see how your app will actually look on the device (the same problem Qt Simulator has). Requirements: Qt4.0+

  • GraphicsView approach - you draw your own stuff, no "classic" layouting, but you can use widgets and custom elements. More whizz, more bang, animation friendly, but requires a LOT of trial-and-error work. Requirements: Qt4.4+

  • MeeGo Touch framework - Features include standardized window navigation, list and other widget behavior, and common theming for components. Also known as MeeGo UI framework. Also known as DirectUI framework. Also known as DUI framework. Requirements: Qt4.6+, MeeGo API

  • MeeGo reference UX (handheld/netbook/etc) - UI implementation based on the MeeGo Touch Framework. Not released yet, so not clear how much customization a "pure meego touch" based app will require to fit in nicely. Requirements: Qt4.6+, MeeGo

  • Orbit - An UI framework, parallel to the MeeGo Touch Framework, initially for use on Symbian devices, but demonstrated to work on Maemo, too. Also known as UI Extensions for Mobile. Also known as Uiemo. Requirements: Qt4.6+, Symbian^4

  • Harmattan UX - like the MeeGo reference UX, but specific to the N900 successor. Requirements: Qt4.6+, MeeGo

  • QML - a Declarative UI tool, in effect a markup language that defines UI elements and their behavior in a declarative manner, allowing, snappy, whizzy UIs. Requirements: Qt4.7+

  • Qt Quick - the Qt User Interface Creation Kit, which consists of QML, a specialized editor in QtCreator and all-around support for the declarative approach. Also known as Qt Declarative. Also known as Declarative UI. Also known as Bauhaus. Requirements: Qt4.7+

To make things more tricky, these overlap a bit, so you can incorporate elements of one into the other, and there are often backports that allow technologies to be tested on previous versions. Also, did get more that four ways... I think I’m going to make a Qt/MeeGo dictionary :)

Venemo 2010-06-12 12:04
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by attila77 (Post 711851)
I used to code in Qt from before the times Maemo existed. The great thing about Qt was that, in gereneal, there WAS no #ifdef required (i you had it, it was considered bad programming or platform incompatibility). Whether you coded for XP, Mac or Linux, you used the same API. It was (still is) a really cool thing.
Yes, it is.
Or more correctly, it would be.

Quote:
Originally Posted by attila77 (Post 711851)
With mobile development this changed - my Maemo apps are already littered with #ifdefs as I want them to compile on my deskop, on Qt4.5 (for N8x0) and Qt4.6 (PR1.2), and chances are there will be another volley of #ifdefs for each release of Qt and each device (worse yet, every firmware release), and my Qt code starts looking as ugly as any bog-standard C++ code that is trying to be multiplatform. And that scares me as a developer, since Qt was supposed to (and did in the past) relieve me from that. And I’m not just talking widget libs here.
Ah, now this is what I was talkig about. :)

If you don't mind, I'm gonna react to each of the ways you described. :)

Quote:
Originally Posted by attila77 (Post 711851)
the "standard widget from code" approach. This will work everywere, look fairly localized but also the one that users usually refer to as "crappy looking community apps". No whizz, no bang. Adaptation already needed due to input technologies (fingerscroll, etc). Requirements: Qt
Well, this is essentially the same as the next one, minus the designer.

Quote:
Originally Posted by attila77 (Post 711851)
QtDesigner approach - similar to above, but using the QtDesigner UI editor. Speeds up UI development by a more visual way of assembling components. The downside is that QtDesigner does not know anything about mobile use, so you are missing out not only on the mobile-specific widgets, but also the generic look and styling - you do not see how your app will actually look on the device (the same problem Qt Simulator has). Requirements: Qt4.0+
This is my current preferred way of doing things.
However, where the standard widgets don't look good enough for a platform, I'm not afraid to use platform-specific stuff.

Quote:
Originally Posted by attila77 (Post 711851)
GraphicsView approach - you draw your own stuff, no "classic" layouting, but you can use widgets and custom elements. More whizz, more bang, animation friendly, but requires a LOT of trial-and-error work. Requirements: Qt4.4+
Seems nice, but way over my current needs.

Quote:
Originally Posted by attila77 (Post 711851)
MeeGo Touch framework - Features include standardized window navigation, list and other widget behavior, and common theming for components. Also known as MeeGo UI framework. Also known as DirectUI framework. Also known as DUI framework. Requirements: Qt4.6+, MeeGo API
Since this is specific to MeeGo, I'm not very happy about using it. There was already an example somewhere - every class name began with "Dui" instead of "Q", very thoughtful.

Okay, for MeeGo-specific look and feel, I will gladly throw in some DuiThis or DuiThat, but building my entire app on these things seems wrong. (Unless the app only targets MeeGo.)

Quote:
Originally Posted by attila77 (Post 711851)
MeeGo reference UX (handheld/netbook/etc) - UI implementation based on the MeeGo Touch Framework. Not released yet, so not clear how much customization a "pure meego touch" based app will require to fit in nicely. Requirements: Qt4.6+, MeeGo
So, this is based on the above, right?
More platform specific stuff, great!

Quote:
Originally Posted by attila77 (Post 711851)
Orbit - An UI framework, parallel to the MeeGo Touch Framework, initially for use on Symbian devices, but demonstrated to work on Maemo, too. Also known as UI Extensions for Mobile. Also known as Uiemo. Requirements: Qt4.6+, Symbian^4
Hm, never heard of this one before, thanks for pointing at it.

Quote:
Originally Posted by attila77 (Post 711851)
Harmattan UX - like the MeeGo reference UX, but specific to the N900 successor. Requirements: Qt4.6+, MeeGo
Very good, this is even more platform specific than anything mentioned.

Quote:
Originally Posted by attila77 (Post 711851)
QML - a Declarative UI tool, in effect a markup language that defines UI elements and their behavior in a declarative manner, allowing, snappy, whizzy UIs. Requirements: Qt4.7+
QML seems great (as a competitor to XAML, I guess?), but it doesn't have anything to do with an app having platform-specific look and feel - rather an app looking the same on every platform.

Quote:
Originally Posted by attila77 (Post 711851)
Qt Quick - the Qt User Interface Creation Kit, which consists of QML, a specialized editor in QtCreator and all-around support for the declarative approach. Also known as Qt Declarative. Also known as Declarative UI. Also known as Bauhaus. Requirements: Qt4.7+
Okay, so this is "just" some tooling for the above, isn't it?

Quote:
Originally Posted by attila77 (Post 711851)
To make things more tricky, these overlap a bit, so you can incorporate elements of one into the other, and there are often backports that allow technologies to be tested on previous versions. Also, did get more that four ways... I think I’m going to make a Qt/MeeGo dictionary :)
This is the part that is great about Qt. We can use whatever things are there together - the right tool for each purpose.

qgil 2010-06-12 12:45
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
attila77, your list of bullets is way too long since it includes repetitions but, most important, it is not related to the naming since both MeeGo and MeeGo-Harmattan will offer you the same choices within the Qt family.

Web Runtime? Plain Qt? Quick? OpenGL ES? Your choice independently of MeeGo, MeeGo-Harmattan or even Symbian. Still not happy and willing to go for MeeGo Touch Framework? Fine for MeeGo and MeeGo-Harmattan.

If you keep yourself in the official API most probably all your headache will be to compile and package separately for MeeGo and MeeGo-Harmattan. But anyway, even within MeeGo rpm you might need to compile native apps more than once to target x86 or different ARM chipsets. All this can be a quite automated process, though.

More than the names, developers will care about the relation between extra work, potential userbase and/or profits. Which is a calculation they are used to do.

attila77 2010-06-12 13:39
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by qgil (Post 711905)
attila77, your list of bullets is way too long since it includes repetitions but, most important, it is not related to the naming since both MeeGo and MeeGo-Harmattan will offer you the same choices within the Qt family.
Take a look at how many ’also know as’-es are there in my list. That’s purely nomenclature, and I wasn’t even overly trying, just listing them off the top of my head. This is not just about the ’provisional naming of MeeGo-Harmattan’, but a general flux of platform related terms and their relations.

Quote:
More than the names, developers will care about the relation between extra work, potential userbase and/or profits. Which is a calculation they are used to do.
What I’m saying (this applies to Venemo’s comment, too) is that there are many choices you need to decide on (not a bad thing in itself), but you need to do far more research than on any other platform to be able to say you’re making a proper engineering/business choice and not guesstimating. No, of course it’s not impossible or rocket science (even though the documentation is practically source-only, but I’ll not count that against the platform as it’s all still prerelease). It’s just that every single mainstream mobile development platform I ever came in contact with requires a lot less effort for a developer to reach the point where he understands exactly what the options are and to be able to utilize them. Qt certainly gives you options/latitude, but at the moment (as said, mainly due to the speed of development), sometimes gives the impression of being a bit short in the focus department.

Jaffa 2010-06-13 12:10
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by qgil (Post 711905)
attila77, your list of bullets is way too long since it includes repetitions [...]
Isn't that an example of the developer mess that's rapidly approaching? If you're saying attila77's list wasn't accurate (and it correlates with my understanding), we've got a problem if one of the leading Qt developers and experts on maemo.org is confused.

Quote:
If you keep yourself in the official API most probably all your headache will be to compile and package separately for MeeGo and MeeGo-Harmattan.
Which is the official API? Is it MeeGo Touch or Qt? If you want to build a "MeeGo" application or a cross-platform (MeeGo, Maemo 5, MeeGo-Harmattan, Symbian) application it's the latter. If you want to build a "MeeGo Handset" application, is MeeGo Touch the official API?

There's overlap here with http://forum.meego.com/showthread.php?t=524&page=2 - but we, as developers are telling you, we're already confused with the relationship between MeeGo-Harmattan, MeeGo and Maemo. Saying "stick with the official API" doesn't help us, we've been developing applications for 5 years and want to migrate them to new platforms with as little work as possible.

Quote:
But anyway, even within MeeGo rpm you might need to compile native apps more than once to target x86 or different ARM chipsets. All this can be a quite automated process, though.
Well, there's been no evidence of handling the production of deb specifics automatically from within the tools which are coming out now; so what's to assume that they'll handle deb *and* RPM packaging details? OBS should help developers at a high-level, but there's all manner of specifics to be hammered out (think dependencies which might be named differently on different platforms).

qgil 2010-06-13 20:39
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Developers: if you don't want confusion just go for the Qt 4.6 API and the Qt SDK. Good for Maemo 5, good for MeeGo 1.0, good for your Symbian work if you are interested and good as a preparation for your MeeGo 1.1 and MeeGo-Harmattan work. If you want to plan further then you have two options: wait for SDK releases with the information your are looking for or choose your preferred Qt based technology based on your own goals or skills. Web Runtime, Quick, QWidget, QGraphicsView and MeeGo Touch fill complementary areas with little overlapping, and probably reading an introduction about each will be enough for you to see what is the best for you and the project you have in mind.

Today the MeeGo official API is the Qt 4.6 API, as detailed at http://meego.com/developers/meego-api

There hasn't been any SDK release of MeeGo 1.1 or MeeGo-Harmattan, and therefore there hasn't been any announcement about their corresponding APIs. Still, Qt 4.7 is already integrated in MeeGo trunk, so Qt 4.7 API is expected for MeeGo 1.1.

And let me insist: this is not a confusion about naming since both MeeGo and MeeGo-Harmattan will have the same Qt offering. If you want to keep discussing about this please kve the related posts in a new thread.

Or even better, go discuss at meego-dev since this is the place where you can find, ask and influence the people working on the MeeGo tools and API.

SkyGoat 2011-01-08 21:11
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by Brank (Post 529708)
I think it's a good name. I can see how you can twist it in to "me ego", but if you can disregard that I don't see a problem.
Sounds catchy, especially if you say it while imitating the hulk. meego store ;)
Sorry I don't like it though it was obviously chosen to point out the mobile aspects of the products using it. Can't say I can come up with something better anyway.

It probably can be construed to mean a half a dozen things. Maybe something in Finnish or Chinese since someone in China has registered Meego.org. I bet China, India, and Africa are the big targets with all these efforts.

Once they get the details of MeeGo to their liking, if I were Nokia, I would be the first handset manufacturer to routinely and for a reasonable price, offer unlocked phones in the US, if they want to play catchup.

I didn't find a MeeGo logo on the MeeGo site though other than those Peeple type characters.

What is their Logo? Is MeeGo going to be a selling point to be marketed or is it going to be Nokia brand that they are going to market? In my opinion marketing MeeGo to devs and manufacturers is fine but to the end customer they'd better stick with Nokia an d just show what the phones can do in the commercials. Nokia was my first phone and I'm sure the first phone of most people out there. I still think they have the most brand recognition world wide when it comes to cell phones.

zehjotkah 2011-01-09 17:21
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
http://wiki.meego.com/MeeGo_Style_Guide
There you can see all variants of the MeeGo logo and also learn how to use it properly.

jainkjohn 2011-01-09 17:31
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
any one seen this?
http://mediacenter.motorola.com/Fact...heet-353b.aspx

sjgadsby 2011-01-09 17:47
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by jainkjohn (Post 915977)
Yes, there are several threads on that device already, and it is off-topic for this thread.

Jedibeeftrix 2011-03-23 13:04
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
since this thread has been resurrected, i might as well put it to good use:

what's the the confusion surrounding the use of harmattan in reference to MeeGo products that has sprung up recently?

various sites seem to be saying that there will be both harmattan and Meego products, i.e. separate and distinct.

what's this about?

Jaffa 2011-03-23 13:32
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by Jedibeeftrix (Post 973857)
what's the the confusion surrounding the use of harmattan in reference to MeeGo products that has sprung up recently?

various sites seem to be saying that there will be both harmattan and Meego products, i.e. separate and distinct.

what's this about?
Nokia's corporate announcements have said they're "still committed to releasing a MeeGo device this year".

Some people have read this as "releasing a MeeGo [project built RPM running] device". However, as far as we know, this is actually meant as "releasing a MeeGo [API compatible] device this year", aka Harmattan.

Therefore there are those who think:
  1. Harmattan's been scrapped and there'll be a "pure" MeeGo device.
  2. Harmattan's being released and then they'll release the "MeeGo device"
  3. Harmattan's being released, and that's what they meant.

I think anyone with any sense believes #3, and I believe - though haven't checked - there are concrete statements from Quim et al which confirm this.

Jedibeeftrix 2011-03-23 13:39
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
thanks. i think that sounds accurate.

Venemo 2011-03-23 13:52
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by Jaffa (Post 973876)
Nokia's corporate announcements have said they're "still committed to releasing a MeeGo device this year".

Some people have read this as "releasing a MeeGo [project built RPM running] device". However, as far as we know, this is actually meant as "releasing a MeeGo [API compatible] device this year", aka Harmattan.

Therefore there are those who think:
  1. Harmattan's been scrapped and there'll be a "pure" MeeGo device.
  2. Harmattan's being released and then they'll release the "MeeGo device"
  3. Harmattan's being released, and that's what they meant.

I think anyone with any sense believes #3, and I believe - though haven't checked - there are concrete statements from Quim et al which confirm this.
I agree with Jaffa on this.
The reason is simple, this is what Quim already said in various forums 100 times already.

SD69 2011-03-23 14:17
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by Venemo (Post 973896)
The reason is simple, this is what Quim already said in various forums 100 times already.
In this Meego Conference Session summary, he actually says it is MeeGo API-compatible with Meego 1.2

http://sf2011.meego.com/program/sess...eego-community

He also openly asks several questions. The important takeaway for us (maemo.org) is that the relationship between the device and Meego project is not yet clarified.

baptx 2011-08-16 14:09
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
I had a question to a video on the old Maemo 6 security platform.
http://www.youtube.com/watch?v=r08dFQQ2uZI
Is there some components that are also used in MeeGo Harmattan?
I think yes because Harmattan is a mix of Maemo and MeeGo and I don't think Nokia would live aside their work they have previoulsy done on Maemo 6. Any ideas?

ajalkane 2011-08-17 11:07
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by baptx (Post 1071160)
Is there some components that are also used in MeeGo Harmattan?
I think yes because Harmattan is a mix of Maemo and MeeGo and I don't think Nokia would live aside their work they have previoulsy done on Maemo 6. Any ideas?
Yes, the security platform is in MeeGo Harmattan. I'm not qualified to assess if that's a good or a bad thing.

inte 2011-11-02 18:52
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by qgil (Post 529073)
This is a simple request to rename this forum but it's worth getting into more details to clarify things.

Harmattan is the name of the software program that comes after Fremantle / Maemo 5. In the Maemo Summit we already announced it as "Maemo 6" in order to bring a clear signal about the major update, change of toolkit, etc.

Now MeeGo comes to the picture. "Maemo 6" will not be used by Nokia as a brand since all the marketing effort around the software platform will be around MeeGo.

To be clear: this is not about "ditching" or "abandoning" any platform. The Harmattan program keeps working with the same plans than last week, no matter the name of the product they will deliver. Maemo 6 and Moblin 2.x merge and have a successor called MeeGo. Current Maemo people will look at it and will say "looks like his mother!". Current Mblin people will look at it and will say "looks like his father!" (or choose your preferred gender) ;) Of course you will see changes compared to Maemo 5, but these changes were coming anyway with Maemo 6.

What does this mean exactly for Harmattan7MeeGo? It means different things for different people:

- For end users nothing really changes, apart from a name most of them were not aware of anyway.

- For application developers not much changes. Harmattan's developer offering is based on Qt 4.6 + Qt Creator, Web Runtime + Aptana. Same for MeeGo and btw same for Symbian. Harmattan *might* have extended APIs unique to Nokia devices (e.g. Ovi APIs), but we'll see and this is part of the MeeGo flexibility anyway. Wait for the SDKs to be released and then we can discuss in more detail. There will be also the APIs available for those willing to use them, provided directly by other open source components in the platform (e.g. GStreamer). Developers will be of course free to use them, at the expense of loosing compatibility with Symbian, and with MeeGo... depends on the component and to be seen as soon as there is a detailed MeeGo architecture public. Then there will be the obvious difference in packaging (deb still for Harmattan, rpm for MeeGo) but this won't be the big issue and anyway compatibility with Symbian implies specific packaging as well.

- For those caring about the platform in depth, Harmattan =! MeeGo. If we would make Harmattan identical to MeeGo then we would need to postpone dates and, really not for a good reason. Not a reason for app developers (the API is there anyway) and not a good reason for end users, who could not care less about packaging and some obscure middleware components. This is the only reason making Ari Jaaksi refer to Harmattan as a "MeeGo instance" instead of just "MeeGo product".

This is why we are dropping the "Maemo 6" *brand* while keeping all the Harmattan development full speed and in the same direction that it was.
Since the MeeGo release which is shipped with the N9 device is actually Maemo 6 and the brand "MeeGo" is officially dead I only wonder why the N9 OS is not renamed back to "Maemo 6" again?
It would also clarify that the N9 is the true N900 sucessor.

chenliangchen 2011-11-09 13:34
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Wish Nokia could rename it back to maemo 6, otherwise lots people thinks N9 is dead.

HtheB 2011-11-09 13:38
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Quote:
Originally Posted by chenliangchen (Post 1120625)
Wish Nokia could rename it back to maemo 6, otherwise lots people thinks N9 is dead.
That is the strategy of S. Elop... All he wants is doing everything so that the N9 is going to grave and make the Windows crap the winner...

Dave999 2012-09-12 06:20
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
I really hope Jolla rename its os. Meego is not a strong brand and is marked with nokia failure. Maemo 7 would be cool, but it's nokia. So the now what

Meego was maemo 6 now it's more meego but again that brand is broken.

Jolt. That would be perfect.

inte 2012-12-23 11:22
Re: Renaming "Maemo 6" to MeeGo / Harmattan
 
Well, Jolla calls it SailfishOs.
SailfishOS is indeed MeeGo, e.g. it features rpm instead of deb-package management.

JohnHughes 2013-03-15 11:54
The future release, codenamed Harmattan.
 
Future release?


All times are GMT. The time now is 21:09.
Page 5 of 5 « First 34 5
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8