>From: ext Till Harbaum / Lists [li...@harbaum.org]
>Sent: Monday, January 03, 2011 2:40 PM
>To: Alhola Kate (Nokia-FNDC/Helsinki)
>Cc: bernd.str...@gmail.com; meego-dev@meego.com
>Subject: Re: [MeeGo-dev] What are the advantages of dev
Hi,
Am Sonntag 02 Januar 2011 schrieb kate.alh...@nokia.com:
> 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.
Ok, that's correct. Yesterday i followed these instructions:
http
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 ke
[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
On Sun, Jan 2, 2011 at 9:47 PM, Till Harbaum / Lists 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
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
run
On Wed, Dec 29, 2010 at 3:45 AM, David Guimard
wrote:
> I thought it was more than clear , it s written in the first page of Meego
> sdk1.1
> the sample located here
> http://meego.gitorious.org/meegotouch/libmeegotouch/trees/master/examples
> + the power of qt graphical view enable all possi
On 12/28/2010 9:21 PM, Ville M. Vainio wrote:
2010/12/28 Till Harbaum / Lists:
Am Dienstag 28 Dezember 2010 schrieb Ville M. Vainio:
QWidgets were not good enough for anybody
You are talking about these QWidgets that several tutorials on the meego
conference were about?
Are you really wonde
>
>From: ext Till Harbaum / Lists [li...@harbaum.org]
>Sent: Tuesday, December 28, 2010 10:27 PM
>To: Alhola Kate (Nokia-FNDC/Helsinki)
>Cc: meego-dev@meego.com
>Subject: Re: [MeeGo-dev] What are the advantages of developing QT apps witho
M. Vainio
> >Cc: meego-dev@meego.com
> >Subject: Re: [MeeGo-dev] What are the advantages of developing QT
> >apps without libmeegotouch over MTF enabled application?
> >
> >On Tue, 28 Dec 2010 21:21:46 +0100
> >"Ville M. Vainio" wrote:
> >
>
eGo-dev] What are the advantages of developing QT apps without
>libmeegotouch over MTF enabled application?
>
>On Tue, 28 Dec 2010 21:21:46 +0100
>"Ville M. Vainio" wrote:
>
>
>>
>> If someone is *still* confused, do let us know and we can make it more
>
On Tue, 28 Dec 2010 20:49:17 +
Dan Leinir Turthra Jensen wrote:
> On Tuesday 28 Dec 2010 20:41:51 Bernd Stramm wrote:
> > On Tue, 28 Dec 2010 21:21:46 +0100
> > "Ville M. Vainio" wrote:
> >
> >
> >
> > > If someone is *still* confused, do let us know and we can make it
> > > more expl
On Tuesday 28 Dec 2010 20:41:51 Bernd Stramm wrote:
> On Tue, 28 Dec 2010 21:21:46 +0100
> "Ville M. Vainio" wrote:
>
>
>
> > If someone is *still* confused, do let us know and we can make it more
> > explicit in the future.
>
> What seems very ironic about the situation is that there appe
On Tue, 28 Dec 2010 21:21:46 +0100
"Ville M. Vainio" wrote:
>
> If someone is *still* confused, do let us know and we can make it more
> explicit in the future.
>
What seems very ironic about the situation is that there appears to be
a new, strict separation between the UX layers for mobi
2010/12/28 Till Harbaum / Lists :
> Am Dienstag 28 Dezember 2010 schrieb Ville M. Vainio:
>> QWidgets were not good enough for anybody
> You are talking about these QWidgets that several tutorials on the meego
> conference were about?
>
> Are you really wondering why developers are confused and l
Hi Kate,
thanks for this reply.
Am Dienstag 28 Dezember 2010 schrieben Sie:
> MeeGo conference presentations at general were not Nokia's (or I think Intel)
> official opinions excluding some keynotes but were just
> selected by content selection board that was just few (4?) persons and so
> mo
On Tuesday, 28 de December de 2010 19:50:35 kate.alh...@nokia.com wrote:
> I promise that we in Forum Nokia do everything to get developers informed as
> well as possible. We release Qt Quick Components pre-alpha as soon as we
> get it done, we released Qt for Maemo5 with first SDK. Reason that you
>
>From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] on behalf of
>ext Till Harbaum / Lists [li...@harbaum.org]
>Sent: Tuesday, December 28, 2010 9:35 PM
>To: meego-dev@meego.com
>Subject: Re: [MeeGo-dev] What are the advant
On Tuesday, 28 de December de 2010 14:37:26 kate.alh...@nokia.com wrote:
> >What is the timescale and roadmap for Qt Quick Components?
>
> Thiago or Henrik Harz can comment this issue ?
As soon as humanly possible. So sometime in Q1 or Q2 in 2011. Hopefully in
time for us to talk about in the Me
Hi,
Am Dienstag 28 Dezember 2010 schrieb Ville M. Vainio:
> QWidgets were not good enough for anybody
You are talking about these QWidgets that several tutorials on the meego
conference were about?
Are you really wondering why developers are confused and loosing confidence in
all this? Do you r
(Sorry about posting at meego-dev - it appears almost nobody is
on-topic on this mailing list, so one more won't hurt).
2010/12/28 Benoît HERVIER :
> Currently it s look like a new technology, require to reconstruct many
> things, isn't ready, and many push for using it. It s look like we are
> d
>
>From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] on behalf of
>ext Benoît HERVIER [kher...@khertan.net]
>Sent: Tuesday, December 28, 2010 5:52 PM
>To: meego-dev@meego.com
>Subject: Re: [MeeGo-dev] What are the advantage
Hi,
>Very big disadvantage to do QWidget application is that you can't get full
>MeeGo handset user experience, you don't have
>sliding stacked windows, portrait orientation / orientation switching support,
>animations etc and you can't do them at
>all with QWidgets ( without doing everything wi
the advantages of developing QT apps without
>libmeegotouch over MTF enabled >application?
>
>On Tue, Dec 28, 2010 at 3:20 PM, Andrew Flegg wrote:
>
>>> With Qt Quick you have all enablers for full MeeGo UX and in Qt Quick
>>> Components you have all UX components ready mad
On Tue, Dec 28, 2010 at 3:20 PM, Andrew Flegg wrote:
>> With Qt Quick you have all enablers for full MeeGo UX and in Qt Quick
>> Components you have all UX components ready made.
>
> Well, not yet. And it's not yet clear what that means in terms of good
> cross-platform support (e.g. Symbian, Ma
eGo-dev] What are the advantages of developing QT apps
> without libmeegotouch over MTF >enabled application?
>
>On Tue, 28 Dec 2010, 13:50:35 GMT, kate.alh...@nokia.com wrote:
>>
>> With Qt Quick you have all enablers for full MeeGo UX and in Qt Quick
>> Compon
On Tue, Dec 28, 2010 at 3:26 PM, Sivan Greenberg wrote:
> A related question for me as I'm going to implement a couple of UXs
> soon, what sort of already ready made "regular" application components
> are available from Qt Quick Components right now?
You can follow the progress (for meego versio
A related question for me as I'm going to implement a couple of UXs
soon, what sort of already ready made "regular" application components
are available from Qt Quick Components right now?
Button, Windows, Dialogs? Can I use everything I would have used using
Qt Designer default mainwindow app ske
On Tue, 28 Dec 2010, 13:50:35 GMT, kate.alh...@nokia.com wrote:
>
> With Qt Quick you have all enablers for full MeeGo UX and in Qt Quick
> Components you have all UX components ready made.
Well, not yet. And it's not yet clear what that means in terms of good
cross-platform support (e.g. Symbia
>From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] on behalf of
>ext Ville M. Vainio [vivai...@gmail.com]
>Sent: Tuesday, December 28, 2010 3:23 PM
>To: Rohit Baravkar; meego-dev
>Subject: Re: [MeeGo-dev] What are the advantages o
Disadvantage with both QWidgets (which is what I assume you mean by Qt w/o
meegotouch) and mtf is that neither is an officially supported solution, i.e.
you are on your own if you use them. If something works today (e.g. gestures),
somebody may decide to break it tomorrow without prior warning.
What are the advantages of developing QT apps without libmeegotouch over MTF
(Meego touch framework) enabled application.?
If we need to implement gestures for any given use case, will a application
based on libmeegotouch be more smoother than QT app without libmeegotouch?
Any touch testing resul
32 matches
Mail list logo
