On 16 Jan 2013, at 18:25, Alan Alpert 4163654...@gmail.com wrote:
On Wed, Jan 16, 2013 at 5:16 AM, Mohamed Fawzi fawzi.moha...@digia.com
wrote:
On 16 Jan 2013, at 10:54, Thomas Hartmann thomas.hartm...@digia.com wrote:
Hi,
[...]
I assume the selected content is also in the app local
On 16 Jan 2013, at 18:14, Alan Alpert 4163654...@gmail.com wrote:
On Wed, Jan 16, 2013 at 1:54 AM, Thomas Hartmann
thomas.hartm...@digia.com wrote:
Hi,
Am 16/01/2013 02:23, schrieb Alan Alpert:
On Tue, Jan 15, 2013 at 8:22 AM, Mohamed Fawzi fawzi.moha...@digia.com
wrote:
I had a long
Hi,
Am 16/01/2013 02:23, schrieb Alan Alpert:
On Tue, Jan 15, 2013 at 8:22 AM, Mohamed Fawzi fawzi.moha...@digia.com
wrote:
I had a long discussion with Thomas, and we came up with yet another
solution :)
This is in a way closer to the initial mail of Alan:
Very close actually. But with
On 16/01/13 02:43, Alan Alpert wrote:
I was talking about just UI. For features we have existing APIs, like
http://doc.qt.digia.com/qtmobility/qsysteminfo.html#hasFeatureSupported
(couldn't find the Qt 5 ex-mobility docs) which could be exposed to
Not part of even Qt Essentials, so not
On 16 Jan 2013, at 10:54, Thomas Hartmann thomas.hartm...@digia.com wrote:
Hi,
Am 16/01/2013 02:23, schrieb Alan Alpert:
On Tue, Jan 15, 2013 at 8:22 AM, Mohamed Fawzi fawzi.moha...@digia.com
wrote:
I had a long discussion with Thomas, and we came up with yet another
solution :)
On Wed, Jan 16, 2013 at 1:54 AM, Thomas Hartmann
thomas.hartm...@digia.com wrote:
Hi,
Am 16/01/2013 02:23, schrieb Alan Alpert:
On Tue, Jan 15, 2013 at 8:22 AM, Mohamed Fawzi fawzi.moha...@digia.com
wrote:
I had a long discussion with Thomas, and we came up with yet another
solution :)
On Wed, Jan 16, 2013 at 5:16 AM, Mohamed Fawzi fawzi.moha...@digia.com wrote:
On 16 Jan 2013, at 10:54, Thomas Hartmann thomas.hartm...@digia.com wrote:
Hi,
[...]
I assume the selected content is also in the app local dir, but you
have a special way to access it without tripping the
I had a long discussion with Thomas, and we came up with yet another solution :)
This is in a way closer to the initial mail of Alan:
1) special place for application local stuff
2) global ordered list of selectors
3) some selectors are static (probably from the make spec), other dynamic
4) 2
On Tue, Jan 15, 2013 at 8:22 AM, Mohamed Fawzi fawzi.moha...@digia.com wrote:
I had a long discussion with Thomas, and we came up with yet another solution
:)
This is in a way closer to the initial mail of Alan:
Very close actually. But with better integration for non-QML applications ;) .
On 10 Jan 2013, at 01:32, Chris Adams
chris.ad...@qinetic.com.aumailto:chris.ad...@qinetic.com.au wrote:
Hi,
This is an interesting topic.
I'm not sure that I'm convinced by anyone's arguments so far, to be honest.
More comments inline:
import paths can achieve basically what we want, so
On 10-Jan-13 17:26, Alan Alpert wrote:
The Qt
heritage so far was, to maximize portability level, to test for
features - something sadly currenly NOT possible in an easy way in QML.
The Qt heritage so far was desktop, where cross-device compatibility
meant make sure it'll still work in
On 10-Jan-13 04:25, Alan Alpert wrote:
So I'll try to replace cross-platform now with cross-device.
\ but I still prefer run-time). Android has the same problem, I have a
lot of apps on my Nexus 7 which either literally or metaphorically do
not work on that device. There are also apps that just
On Thu, Jan 10, 2013 at 4:16 AM, Attila Csipa q...@csipa.in.rs wrote:
On 10-Jan-13 04:25, Alan Alpert wrote:
So I'll try to replace cross-platform now with cross-device.
\ but I still prefer run-time). Android has the same problem, I have a
lot of apps on my Nexus 7 which either literally or
On 01/08/2013 06:54 PM, Alan Alpert wrote:
Do you have an example of how this could be done? Specifically,
something that could select a different settings.js file for SameGame
without having to go through the C++ executable?
If by without having to go through the C++ executable you mean that
On 08-Jan-13 18:54, Alan Alpert wrote:
It seems to me that this is a problem which can/should be solved at the
build system level.
I had the impression that it shouldn't be solved at the build system
level (even though it can be). That breaks QML as an interpreted
language, which is a
Mardegan
Cc: development
Subject: Re: [Development] Platform Content Selection
On Tue, Jan 8, 2013 at 3:17 AM, Alberto Mardegan
ma...@users.sourceforge.net wrote:
On 01/08/2013 02:03 AM, Alan Alpert wrote:
Feedback?
It's really Qt that's cross-platform focused now, not me. I just want
this so
From: development-bounces+fawzi.mohamed=digia@qt-project.org
[development-bounces+fawzi.mohamed=digia@qt-project.org] on behalf of
Attila Csipa [q...@csipa.in.rs]
Sent: Wednesday, January 09, 2013 11:58 AM
To: development@qt-project.org
Subject: Re: [Development] Platform Content Selection
From: development-bounces+fawzi.mohamed=digia@qt-project.org
[development-bounces+fawzi.mohamed=digia@qt-project.org] on behalf of
Alberto Mardegan [ma...@users.sourceforge.net]
Sent: Wednesday, January 09, 2013 9:26 AM
To: development
Subject: Re: [Development] Platform Content Selection
On Wed, Jan 9, 2013 at 12:26 AM, Alberto Mardegan
ma...@users.sourceforge.net wrote:
On 01/08/2013 06:54 PM, Alan Alpert wrote:
Do you have an example of how this could be done? Specifically,
something that could select a different settings.js file for SameGame
without having to go through the
On Wed, Jan 9, 2013 at 6:39 AM, Mohamed Fawzi fawzi.moha...@digia.com wrote:
In general I think that at least for development using several directories
with sensible fallbacks is the way to go:
One wants to have the possibility of overriding just some files on a
platform, while still having
On Mon, Jan 07, 2013 at 05:03:05PM -0800, Alan Alpert wrote:
With the new cross-platform focus, we need some way for QML to
load platform specific content at runtime. [...]
It's really Qt that's cross-platform focused now, not me. [...]
These are interesting statements.
Given that being
Hi,
This is an interesting topic.
I'm not sure that I'm convinced by anyone's arguments so far, to be honest.
More comments inline:
import paths can achieve basically what we want, so for example
high_res/bla.qml will override bla.qml if the path is something like
high_res:. .
This should
On Wed, Jan 9, 2013 at 1:30 PM, André Pönitz
andre.poen...@mathematik.tu-chemnitz.de wrote:
On Mon, Jan 07, 2013 at 05:03:05PM -0800, Alan Alpert wrote:
With the new cross-platform focus, we need some way for QML to
load platform specific content at runtime. [...]
It's really Qt that's
On Wed, Jan 9, 2013 at 4:32 PM, Chris Adams chris.ad...@qinetic.com.au wrote:
Hi,
This is an interesting topic.
I'm not sure that I'm convinced by anyone's arguments so far, to be honest.
More comments inline:
import paths can achieve basically what we want, so for example
On 08-Jan-13 02:03, Alan Alpert wrote:
What I suggest is a path based swap-out like Plasma has, but a little
more generic than being tied into the Plasma Package format. Here's
the basic algorithm for swapping, where platformSelectors is an
ordered list of selectors specified for the platform
On 01/08/2013 02:03 AM, Alan Alpert wrote:
Feedback?
It's really Qt that's cross-platform focused now, not me. I just want
this so that SameGame runs beautifully on BB10 :) . So while I'd
welcome feedback from any source, I *need* to hear it from people
interested in other platforms (or even
On Tue, Jan 8, 2013 at 1:45 AM, Attila Csipa q...@csipa.in.rs wrote:
On 08-Jan-13 02:03, Alan Alpert wrote:
What I suggest is a path based swap-out like Plasma has, but a little
more generic than being tied into the Plasma Package format. Here's
the basic algorithm for swapping, where
On Tue, Jan 8, 2013 at 3:17 AM, Alberto Mardegan
ma...@users.sourceforge.net wrote:
On 01/08/2013 02:03 AM, Alan Alpert wrote:
Feedback?
It's really Qt that's cross-platform focused now, not me. I just want
this so that SameGame runs beautifully on BB10 :) . So while I'd
welcome feedback
The reason qmlmin or a qml-defs-processor could work is that it's
purely optimization. The QML code works exactly the same with and
without it, so you can develop with the un-processed QML and then get
a speed boost for the final deployment.
I should also mention that this is also how QRC
With the new cross-platform focus, we need some way for QML to load
platform specific content at runtime. I've put the in-depth why
essay on my blog (http://alan.imagin-itis.net/?p=416) - most people
have been telling me this for years and thus need no convincing. But I
think that as a
30 matches
Mail list logo