On Dec 24, 2012, at 8:22 AM, Alan Alpert <4163654...@gmail.com> wrote:
> For those interested in the matter, the discussion has now moved to
> codereview.
>
> https://codereview.qt-project.org/#change,43539 adds the QQmlApplicationEngine
> https://codereview.qt-project.org/#change,43540 adds the
On Mon, Jan 14, 2013 at 7:12 AM, Koehne Kai wrote:
>
>...
>
> So your idea is to consolidate on one qml binary, effectively deprecating
> qmlviewer and qmlscene? Sounds like a plan. I don't think we've 'deprecated'
> binaries in Qt before, but I personally don't see a big problem even removing
> -Original Message-
> From: Alan Alpert [mailto:4163654...@gmail.com]
> Sent: Thursday, January 10, 2013 5:11 PM
> To: Koehne Kai
> Cc: Sorvig Morten; development@qt-project.org
> Subject: Re: [Development] QML Runtime
>
> On Wed, Jan 9, 2013 at 11:57
On Wed, Jan 9, 2013 at 11:57 PM, Koehne Kai wrote:
>
>
>> -Original Message-
>> From: Alan Alpert [mailto:4163654...@gmail.com]
>> Sent: Wednesday, January 09, 2013 4:11 PM
>> To: Koehne Kai
>> Cc: Sorvig Morten; development@qt-project.org
>&
From: Alan Alpert [4163654...@gmail.com]
Sent: Wednesday, January 09, 2013 5:19 PM
To: Mohamed Fawzi
Subject: Re: [Development] QML Runtime
The qml binary is supposed to be the solution to the split. Let it be
the one binary, and qmlscene/qmlviewer can be deprecated.
--
Alan Alpert
PS: Did
> -Original Message-
> From: Alan Alpert [mailto:4163654...@gmail.com]
> Sent: Wednesday, January 09, 2013 4:11 PM
> To: Koehne Kai
> Cc: Sorvig Morten; development@qt-project.org
> Subject: Re: [Development] QML Runtime
>
> On Wed, Jan 9, 2013 at 12:41
On Wed, Jan 9, 2013 at 12:41 AM, Koehne Kai wrote:
>> -Original Message-
>> From: Alan Alpert [mailto:4163654...@gmail.com]
>> Sent: Tuesday, January 08, 2013 5:43 PM
>> To: Koehne Kai
>> Cc: Sorvig Morten; development@qt-project.org
>> Su
> -Original Message-
> From: Alan Alpert [mailto:4163654...@gmail.com]
> Sent: Tuesday, January 08, 2013 5:43 PM
> To: Koehne Kai
> Cc: Sorvig Morten; development@qt-project.org
> Subject: Re: [Development] QML Runtime
>
> [..]
> Technically you could achieve
On Tue, Jan 8, 2013 at 9:32 AM, Mohamed Fawzi wrote:
> I understand the attractiveness of small tools, especially if one wants to
> deploy bundling that tool.
> Still I am with Kay on this, I see the probability of diverging, and thus
> having more bugs, that happen only in one tool and not the
-project.org
Subject: Re: [Development] QML Runtime
On Tue, Jan 8, 2013 at 4:56 AM, Koehne Kai wrote:
>> -Original Message-
>> From: Alan Alpert [mailto:4163654...@gmail.com]
>> Sent: Monday, December 24, 2012 8:23 AM
>> To: Koehne Kai
>> Cc: Sorvig Morten; develop
On Tue, Jan 8, 2013 at 4:56 AM, Koehne Kai wrote:
>> -Original Message-
>> From: Alan Alpert [mailto:4163654...@gmail.com]
>> Sent: Monday, December 24, 2012 8:23 AM
>> To: Koehne Kai
>> Cc: Sorvig Morten; development@qt-project.org
>> Subject: Re:
> -Original Message-
> From: Alan Alpert [mailto:4163654...@gmail.com]
> Sent: Monday, December 24, 2012 8:23 AM
> To: Koehne Kai
> Cc: Sorvig Morten; development@qt-project.org
> Subject: Re: [Development] QML Runtime
>
> For those interested in the matter, the
> -Original Message-
>> From: development-bounces+kai.koehne=digia@qt-project.org
>> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
>> Behalf Of Sorvig Morten
>> Sent: Thursday, December 13, 2012 4:55 PM
>> To: development@qt-project.org
&
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
> Behalf Of Sorvig Morten
> Sent: Thursday, December 13, 2012 4:55 PM
> To: development@qt-project.org
> Subject:
On Dec 13, 2012, at 2:06 PM, Koehne Kai wrote:
>
> It's there because there are different conventions on different OS where the
> .qml files should be (relative to the binary). E.g. on Mac its unter
> .app/Contents/Resources, on QNX it's app/native, on Android it's "assets:/" …
This is a depl
ect.org
> Subject: Re: [Development] QML Runtime
>
> [...]
> It wouldn't include QtQuick2ApplicationViewer, but that's more because I
> don't think QtQuick2ApplicationViewer needs to exist. Looking at it right
> now, what it provides is
> A) A QQuickView (you c
On Wed, Dec 12, 2012 at 4:04 PM, Chris Adams wrote:
> Hi,
>
>
>> maybe there's a case for adding a small QQmlApplicationEngine in QtQml
>> which adds the application runtime aspects?
>
>
> It's early and I haven't had my second coffee yet, so maybe I'm
> misunderstanding something, but are these a
Hi,
maybe there's a case for adding a small QQmlApplicationEngine in QtQml
> which adds the application runtime aspects?
>
It's early and I haven't had my second coffee yet, so maybe I'm
misunderstanding something, but are these application runtime aspects
completely non-gui, non-QtQuick related?
On Tue, Dec 11, 2012 at 11:33 PM, Sorvig Morten wrote:
>
> On Dec 11, 2012, at 8:30 PM, Alan Alpert <4163654...@gmail.com> wrote:
>
>> On Tue, Dec 11, 2012 at 3:33 AM, Sorvig Morten
>> wrote:
>>> Please bundle the QML runtime in a class that the app author can
>>> instantiate.
>>>
>>> This give
On Dec 11, 2012, at 8:30 PM, Alan Alpert <4163654...@gmail.com> wrote:
> On Tue, Dec 11, 2012 at 3:33 AM, Sorvig Morten
> wrote:
>> Please bundle the QML runtime in a class that the app author can instantiate.
>>
>> This gives us the flexibility to handle platform differences and integrate
>>
On 12/12/12 05:38, Alan Alpert wrote:
> What would a ~/.qmlrc file contain?
Anything if it's just a QML script. I see it as extra convenience that a
simple "qml somescript" invocation could load /etc/qmlrc *and* ~/.qmlrc
(override), if they exist, to customize the current qml instance.
I really l
On Tue, Dec 11, 2012 at 4:53 AM, Shawn Rutledge
wrote:
> I like all the ideas mentioned so far on this thread. Here's a couple more:
>
> IMO there needs to be some QML 2 tool which adds back most of the features
> that qmlviewer already had. They could be optionally-loaded plugins perhaps,
> but
On Tue, Dec 11, 2012 at 3:33 AM, Sorvig Morten wrote:
> Please bundle the QML runtime in a class that the app author can instantiate.
>
> This gives us the flexibility to handle platform differences and integrate
> with existing workflows. There can still be a "qmlscene"-like binary that
> would
On Tue, Dec 11, 2012 at 8:00 AM, Thiago Macieira
wrote:
> On terça-feira, 11 de dezembro de 2012 10.48.43, Knoll Lars wrote:
>> > The main difficulty I see is how to determine which application class to
>> > instantiate.
>> >
>> > If you load a non-UI QML file you might not want QGuiApplication to
On Tue, Dec 11, 2012 at 12:45 AM, Ziller Eike wrote:
>
> On 11.12.2012, at 09:34, Mark wrote:
>
>> On Tue, Dec 11, 2012 at 4:44 AM, Alan Alpert <4163654...@gmail.com> wrote:
>>> I'd like to remind people that qmlviewer and qmlscene are not meant
>>> ...
>>
>> Ohh.. qmlviewer and qmlscene are not
On terça-feira, 11 de dezembro de 2012 10.48.43, Knoll Lars wrote:
> > The main difficulty I see is how to determine which application class to
> > instantiate.
> >
> > If you load a non-UI QML file you might not want QGuiApplication to be
> > instantiated.
> > If you load a QtQuick1 file you'll ne
On Tuesday, 2012-12-11, Knoll Lars wrote:
> On Dec 11, 2012, at 12:15 PM, Kevin Krammer wrote:
> > On Tuesday, 2012-12-11, Knoll Lars wrote:
> >> On Dec 11, 2012, at 10:47 AM, Kevin Krammer
> >> wrote:
> >>> If you load a BB10 Cascades application you'll need a
> >>> bb::cascades::Application (w
I like all the ideas mentioned so far on this thread. Here's a couple more:
IMO there needs to be some QML 2 tool which adds back most of the features
that qmlviewer already had. They could be optionally-loaded plugins perhaps,
but it shouldn't be a lot of trouble to start up the new viewer wit
On Dec 11, 2012, at 12:15 PM, Kevin Krammer wrote:
> On Tuesday, 2012-12-11, Knoll Lars wrote:
>> On Dec 11, 2012, at 10:47 AM, Kevin Krammer
>>
>> wrote:
>>> On Tuesday, 2012-12-11, Alan Alpert wrote:
>
One big difference would be less flexibility about the invocation. As
a debuggi
Please bundle the QML runtime in a class that the app author can instantiate.
This gives us the flexibility to handle platform differences and integrate with
existing workflows. There can still be a "qmlscene"-like binary that would
simply instantiate the class.
- Morten
_
On Tuesday, 2012-12-11, Knoll Lars wrote:
> On Dec 11, 2012, at 10:47 AM, Kevin Krammer
>
> wrote:
> > On Tuesday, 2012-12-11, Alan Alpert wrote:
> >> One big difference would be less flexibility about the invocation. As
> >> a debugging tool qmlscene needs to be able to run smaller "units" of
On Dec 11, 2012, at 10:47 AM, Kevin Krammer
wrote:
> On Tuesday, 2012-12-11, Alan Alpert wrote:
>
>> Goal: "qml" application. Something you can use like "qml main.qml" on
>> a linux system, or "./main.qml" where main.qml starts with
>> "#!/usr/bin/qml". I have no idea how this is supposed to w
On Tuesday, 2012-12-11, Alan Alpert wrote:
> Goal: "qml" application. Something you can use like "qml main.qml" on
> a linux system, or "./main.qml" where main.qml starts with
> "#!/usr/bin/qml". I have no idea how this is supposed to work on
> windows or mac, but I'm sure there's some equivalent
On 11.12.2012, at 09:34, Mark wrote:
> On Tue, Dec 11, 2012 at 4:44 AM, Alan Alpert <4163654...@gmail.com> wrote:
>> I'd like to remind people that qmlviewer and qmlscene are not meant
>> for deploying applications. They are not a complete runtime, they are
>> only meant for debugging. But the f
On Dec 11, 2012, at 9:34 AM, Mark
wrote:
> On Tue, Dec 11, 2012 at 4:44 AM, Alan Alpert <4163654...@gmail.com> wrote:
>> I'd like to remind people that qmlviewer and qmlscene are not meant
>> for deploying applications. They are not a complete runtime, they are
>> only meant for debugging. But
On Tue, Dec 11, 2012 at 4:44 AM, Alan Alpert <4163654...@gmail.com> wrote:
> I'd like to remind people that qmlviewer and qmlscene are not meant
> for deploying applications. They are not a complete runtime, they are
> only meant for debugging. But the fact that people keep wanting to use
> them fo
I'd like to remind people that qmlviewer and qmlscene are not meant
for deploying applications. They are not a complete runtime, they are
only meant for debugging. But the fact that people keep wanting to use
them for their applications suggests that it might be worth providing
a complete runtime.
37 matches
Mail list logo
