Re: [MeeGo-dev] What are the advantages of developing QT apps without libmeegotouch over MTF enabled application?

2011-01-02 Thread Till Harbaum / Lists
Hi,

Am Dienstag 28 Dezember 2010 schrieb Bernd Stramm:
 What seems very ironic about the situation is that there appears to be
 a new, strict separation between the UX layers for mobile and desktop.
Speaking of this: 

I have meegotouch running native on my ubuntu desktop, i have qtmobility 
running native there, i have the latest qtcreator 2.1.0beta and still i can't 
run meego qml apps:

file:///home/harbaum/projekte/meego/apps/qt-components/gallery/positionindicator.qml:28:1:
 module com.meego is not installed 
 import com.meego 1.0 

What am i doing wrong? Or is exactly this caused by the fact, that nokia tries 
to fragment qt into desktop and mobile versions and i won't be able to run 
meego apps on the desktop without using emulation?

Till
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] What are the advantages of developing QT apps without libmeegotouch over MTF enabled application?

2011-01-02 Thread Ville M. Vainio
On Sun, Jan 2, 2011 at 9:47 PM, Till Harbaum / Lists li...@harbaum.org wrote:

 I have meegotouch running native on my ubuntu desktop, i have qtmobility 
 running native there, i have the latest qtcreator 2.1.0beta and still i can't 
 run meego qml apps:

 file:///home/harbaum/projekte/meego/apps/qt-components/gallery/positionindicator.qml:28:1:
  module com.meego is not installed
     import com.meego 1.0

 What am i doing wrong? Or is exactly this caused by the fact, that nokia 
 tries to fragment qt into desktop and mobile versions and i won't be able to 
 run meego apps on the desktop without using emulation?

There are qt quick components (PREVIEW) packages for Ubuntu:

http://qt-funk.blogspot.com/2010/10/fresh-from-oven-qt-extras-for-ubuntu.html

(the same place, fn-ppa, has MTF as well, since it's a dependency of QtQC).

-- 
Ville M. Vainio @@ Forum Nokia
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] What are the advantages of developing QT apps without libmeegotouch over MTF enabled application?

2011-01-02 Thread kate.alhola


From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] on behalf of 
ext Till Harbaum / Lists [li...@harbaum.org]
Sent: Sunday, January 02, 2011 9:47 PM
To: Bernd Stramm
Cc: meego-dev@meego.com
Subject: Re: [MeeGo-dev] What are the advantages of developing QT apps  
without libmeegotouch over MTF enabled application?


Am Dienstag 28 Dezember 2010 schrieb Bernd Stramm:
 What seems very ironic about the situation is that there appears to be
 a new, strict separation between the UX layers for mobile and desktop.
Speaking of this:

I have meegotouch running native on my ubuntu desktop, i have qtmobility 
running native there, i have the latest qtcreator 2.1.0beta and still i can't 
run meego qml apps:

file:///home/harbaum/projekte/meego/apps/qt-components/gallery/positionindicator.qml:28:1:
 module com.meego is not installed
 import com.meego 1.0

You have not yet installed Qt Components package, exactly same way that you 
need include and link
libraries in C++ Qt, you need import Component libraries for Qml. 

What am i doing wrong? Or is exactly this caused by the fact, that nokia tries 
to fragment qt into desktop and mobile versions and i won't be able to run 
meego apps on the desktop without using emulation?

There will be components for both Mobile MeeGo and Symbian and also Desktop 
version.

Qt Components are reducing fragmentation, first time there is toolkit 
supporting Both MeeGo and Symbian in Mobile
and all desktop environments.

Kate


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] What are the advantages of developing QT apps without libmeegotouch over MTF enabled application?

2011-01-02 Thread Clark, Joel

Am Dienstag 28 Dezember 2010 schrieb Bernd Stramm:
 What seems very ironic about the situation is that there appears to be
 a new, strict separation between the UX layers for mobile and desktop.


The current MeeGo desktop UX is mostly a port of the Moblin Clutter/Mutter 
based desktop UX for keyboard based systems to MeeGo 1.0 and has been in 
sustaining ever since while a lot of new development has been done on the touch 
based UX for mobile etc. A lot has changed since the desktop UX was designed.

regards
Joel



___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] MeeGo 1.2 Roadmap?

2011-01-02 Thread jukka.eklund
Hi,

It's a fair question :)

But I'm wondering what kind of information you are looking for, or actually 
what kind of format? As you know all the information is on featurezilla, for 
everybody to see.

You can do queries like this:
http://bugs.meego.com/report.cgi?x_axis_field=producty_axis_field=componentz_axis_field=query_format=report-tableshort_desc_type=allwordssubstrshort_desc=classification=MeeGo+Featuresproduct=MeeGo+Connected+TV+Featuresproduct=MeeGo+Core+OS+Featuresproduct=MeeGo+Handset+Featuresproduct=MeeGo+IVI+Featuresproduct=MeeGo+Netbook+Featuresproduct=MeeGo+SDK+featuresproduct=MeeGo+Tablet+Featuresversion=1.2version=1.2longdesc_type=allwordssubstrlongdesc=bug_file_loc_type=allwordssubstrbug_file_loc=deadlinefrom=deadlineto=emailassigned_to1=1emailtype1=substringemail1=emailassigned_to2=1emailreporter2=1emailqa_contact2=1emailcc2=1emailtype2=substringemail2=bugidtype=includebug_id=votes=chfieldfrom=chfieldto=Nowchfieldvalue=format=tableaction=wrapfield0-0-0=nooptype0-0-0=noopvalue0-0-0=
(all Accepted 1.2 features in products, grouped to components)

BTW, for Handset there is some material already in 
http://wiki.meego.com/Roadmap, in the form of high-level presentation from 
MeeGo conference.

Jukka

 -Original Message-
 From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com]
 On Behalf Of ext Carsten Munk
 Sent: 2. tammikuuta 2011 0:29
 To: meego-dev; Hindman, Gavin; Pienimaki Sami (Nokia-MS/Tampere);
 Rudolf Streif; Lavonius Ville (Nokia-MS/Helsinki)
 Subject: [MeeGo-dev] MeeGo 1.2 Roadmap?
 
 Hi,
 
 So, we're in 2011, we have a release 1.2 in about 4-5 months - and I
 wondered, what do we intend on delivering?
 
 I went to http://wiki.meego.com/Roadmap and looked, finding that we
 have a release plan (always good..) and plans related to the build
 infrastructure.. But no Core/Handset/IVI/SDK roadmaps. Nor on
 meego.com anywhere.
 
 The question is - and I think it's a fairly reasonable one: Where is
 our Core, Handset, Netbook, IVI and SDK roadmaps for 1.2? It's not on
 meego.com anywhere - how does our future platform 'customers' know
 what we plan to have coming for MeeGo 1.2?
 
 And second: What is the current status of them - where can I see the
 work in progress? Is there some featurezilla searches?
 
 Gavin, Sami, Rudolf, Ville and the rest of you guys responsible for
 MeeGo roadmaps - could I ask you to spend some few minutes elaborating
 to the rest of the project what's going on in Program Office regarding
 the roadmaps for 1.2 for your areas? It'll help people understand why
 these roadmaps may be missing and set up expectations to when we'll
 see them :)
 
 Thank you in advance,
 
 BR
 Carsten Munk
 MeeGo Nokia N900 hardware adaptation maintainer
 ___
 MeeGo-dev mailing list
 MeeGo-dev@meego.com
 http://lists.meego.com/listinfo/meego-dev
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] MeeGo 1.2 Roadmap?

2011-01-02 Thread Carsten Munk
2011/1/3  jukka.ekl...@nokia.com:
 Hi,

 It's a fair question :)

 But I'm wondering what kind of information you are looking for, or actually 
 what kind of format? As you know all the information is on featurezilla, for 
 everybody to see.

 You can do queries like this:
 http://bugs.meego.com/report.cgi?x_axis_field=producty_axis_field=componentz_axis_field=query_format=report-tableshort_desc_type=allwordssubstrshort_desc=classification=MeeGo+Featuresproduct=MeeGo+Connected+TV+Featuresproduct=MeeGo+Core+OS+Featuresproduct=MeeGo+Handset+Featuresproduct=MeeGo+IVI+Featuresproduct=MeeGo+Netbook+Featuresproduct=MeeGo+SDK+featuresproduct=MeeGo+Tablet+Featuresversion=1.2version=1.2longdesc_type=allwordssubstrlongdesc=bug_file_loc_type=allwordssubstrbug_file_loc=deadlinefrom=deadlineto=emailassigned_to1=1emailtype1=substringemail1=emailassigned_to2=1emailreporter2=1emailqa_contact2=1emailcc2=1emailtype2=substringemail2=bugidtype=includebug_id=votes=chfieldfrom=chfieldto=Nowchfieldvalue=format=tableaction=wrapfield0-0-0=nooptype0-0-0=noopvalue0-0-0=
 (all Accepted 1.2 features in products, grouped to components)

 BTW, for Handset there is some material already in 
 http://wiki.meego.com/Roadmap, in the form of high-level presentation from 
 MeeGo conference.


Hi,

Thanks for pointing this out :) I guess some customized featurezilla
queries added to the roadmap wiki pages to help list those would go a
long way, so we have something to point people to.

What I'm looking for is basically a listing of the features accepted
on the roadmap for 1.2 for various areas.

For people/companies interested in contributing, 'NEW' listings could
be useful for seeing what they can propose to be responsible for, in
order to get it implemented.

The current links point to features with indefinition and new, which
doesn't help to clear up the picture of what's going to be
delivered/planned.

In addition to the featurezilla stuff, some information about
deadlines for 'ACCEPTED' for 1.2 and when 1.3 planning starts, would
be useful - some insight in your processes, if any exist :)

Best regards,
Carsten Munk


 -Original Message-
 From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com]
 On Behalf Of ext Carsten Munk
 Sent: 2. tammikuuta 2011 0:29
 To: meego-dev; Hindman, Gavin; Pienimaki Sami (Nokia-MS/Tampere);
 Rudolf Streif; Lavonius Ville (Nokia-MS/Helsinki)
 Subject: [MeeGo-dev] MeeGo 1.2 Roadmap?

 Hi,

 So, we're in 2011, we have a release 1.2 in about 4-5 months - and I
 wondered, what do we intend on delivering?

 I went to http://wiki.meego.com/Roadmap and looked, finding that we
 have a release plan (always good..) and plans related to the build
 infrastructure.. But no Core/Handset/IVI/SDK roadmaps. Nor on
 meego.com anywhere.

 The question is - and I think it's a fairly reasonable one: Where is
 our Core, Handset, Netbook, IVI and SDK roadmaps for 1.2? It's not on
 meego.com anywhere - how does our future platform 'customers' know
 what we plan to have coming for MeeGo 1.2?

 And second: What is the current status of them - where can I see the
 work in progress? Is there some featurezilla searches?

 Gavin, Sami, Rudolf, Ville and the rest of you guys responsible for
 MeeGo roadmaps - could I ask you to spend some few minutes elaborating
 to the rest of the project what's going on in Program Office regarding
 the roadmaps for 1.2 for your areas? It'll help people understand why
 these roadmaps may be missing and set up expectations to when we'll
 see them :)

 Thank you in advance,

 BR
 Carsten Munk
 MeeGo Nokia N900 hardware adaptation maintainer
 ___
 MeeGo-dev mailing list
 MeeGo-dev@meego.com
 http://lists.meego.com/listinfo/meego-dev

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev