Re: [Development] Nominating Ulf Hermann as approver

+1 On 4 Mar 2014, at 13:51, Simon Hausmann wrote: > Hi, > > I'd like to nominate Ulf for approvership. He's been hacking on various bits > and pieces in the profiler support in Qml and he also implemented a brand new > profiler for the JavaScript engine. > > I'm convinced that he would make a

Re: [Development] Qmake variable for iOS

Hi, qmake for ios is a bit strange, in the sense that it treats device and simulator as two build versions. This is like debug and release, setting it in CONFIG sets the default used in Makefile, but it also still generates specific makefiles for each possible combination (iphoneos debug/relas

Re: [Development] Qmake variable for iOS

Hi, qmake for ios is a bit strange, in the sense that it treats device and simulator as two build versions. This is like debug and release, setting it in CONFIG sets the default used in Makefile, but it also still generates specific makefiles for each possible combination (iphoneos debug/relas

Re: [Development] Remove OSX 10.6 Build?

On 21 Jan 2014, at 14:25, Jake Petroules mailto:jake.petrou...@petroules.com>> wrote: On Jan 21, 2014, at 7:36 AM, Sorvig Morten mailto:morten.sor...@digia.com>> wrote: On 21 Jan 2014, at 11:51, Simon Hausmann mailto:simon.hausm...@digia.com>> wrote: That depends on how much time we spend r

Re: [Development] qtest-qml osx

By the way if you still have crashes with QtCreator please file a bug also about them. cheers Fawzi On 6 Jan 2014, at 17:15, Joshua Kolden wrote: > Thanks, that’s helpful. I didn’t think to just use an import in the qml test > file itself. I’ll test today, but it doesn’t seem like that would

Re: [Development] registering vnd.qt.*qml types

the list has moved to the media-ty...@ietf.org<mailto:media-ty...@ietf.org> mailing list. look there for the discussion. Fawzi On 29 Jan 2013, at 14:26, Mohamed Fawzi mailto:fawzi.moha...@digia.com>> wrote: Hi, sorry for the noise, I had the wrong ML address. after some discu

[Development] registering vnd.qt.*qml types

Hi, sorry for the noise, I had the wrong ML address. after some discussion on the development@qt-project.org mailing list we http://qt-project.org/ decided to register some qml http://qt-project.org/wiki/Introduction_to_Qt_Quick types in the vendor tree. Before

Re: [Development] Runtime Platform Content Selection

On 17 Jan 2013, at 14:35, Sorvig Morten wrote: > > On Jan 16, 2013, at 5:16 PM, Attila Csipa wrote: > >> On 16/01/13 17:36, Mohamed Fawzi wrote: >>> I am certainly not against the idea of a faster/more efficient static way >>> of choosing resources but it

Re: [Development] Platform Content Selection

On 16 Jan 2013, at 18:14, Alan Alpert <4163654...@gmail.com> wrote: > On Wed, Jan 16, 2013 at 1:54 AM, Thomas Hartmann > wrote: >> Hi, >> >> Am 16/01/2013 02:23, schrieb Alan Alpert: >>> On Tue, Jan 15, 2013 at 8:22 AM, Mohamed Fawzi >>> wrot

Re: [Development] Platform Content Selection

On 16 Jan 2013, at 18:25, Alan Alpert <4163654...@gmail.com> wrote: > On Wed, Jan 16, 2013 at 5:16 AM, Mohamed Fawzi > wrote: >> >> On 16 Jan 2013, at 10:54, Thomas Hartmann wrote: >> >>> Hi, >>> [...] >>>> I assume the select

Re: [Development] Proposal: expose the OS/platform in QML

On 16 Jan 2013, at 17:37, Alan Alpert <4163654...@gmail.com> wrote: > On Wed, Jan 16, 2013 at 2:22 AM, Rutledge Shawn > wrote: >> On 16 Jan 2013, at 8:21 AM, Bache-Wiig Jens wrote: >> >>> True. It is exactly what we would use to implement the platform selector. >>> But it can also be more pow

Re: [Development] Runtime Platform Content Selection

On 16 Jan 2013, at 10:28, Bache-Wiig Jens wrote: > > On Jan 15, 2013, at 1:39 PM, Mohamed Fawzi wrote: > >> In the Platform Content Selection thread some saw runtime selection as not >> needed. >> I disagree, as I think it could be very useful in some occa

Re: [Development] Platform Content Selection

On 16 Jan 2013, at 10:54, Thomas Hartmann wrote: > Hi, > > Am 16/01/2013 02:23, schrieb Alan Alpert: >> On Tue, Jan 15, 2013 at 8:22 AM, Mohamed Fawzi >> wrote: >>> I had a long discussion with Thomas, and we came up with yet another >>> solution :)

Re: [Development] Platform Content Selection

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 URL

[Development] Runtime Platform Content Selection

In the Platform Content Selection thread some saw runtime selection as not needed. I disagree, as I think it could be very useful in some occasions (high_res/low_res, different orientation,…). I do not believe that having a separate binary for all those things is the correct choice. Still the is

Re: [Development] Qml mime types

:44, Mohamed Fawzi wrote: > 2 obviously needs more than 256, and magic solving in general needs more > resources, so that the mime resolution algorithm tries to avoid it if > possible, and soem applications might not do it at all (if they don't have > the content of the f

[Development] Qml what for, was Platform Content Selection

On 9 Jan 2013, at 22:30, André Pönitz wrote: > […] > A few questions that come to mind are: I think these are good provocative questions, and I will try to answer them with my personal opinion. > > - Which real world problems do we address? [By "real world" I > explicitly do include handset

Re: [Development] Platform Content Selection

On 10 Jan 2013, at 01:32, Chris Adams mailto: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 > high_res/bl

[Development] QML Runtime

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

Re: [Development] Qml mime types

ik.tu-chemnitz.de] Sent: Thursday, January 10, 2013 12:24 AM To: Mohamed Fawzi Cc: Rutledge Shawn; development@qt-project.org Subject: Re: [Development] Qml mime types On Tue, Jan 08, 2013 at 05:44:05PM +0000, Mohamed Fawzi wrote: > That is a good point, currently the license is 1393 characters

Re: [Development] Platform Content Selection

The import path solution is exactly what I think looks like the best solution. For the qrc approach, the "first wins" approach makes it more usable, still I would like to see a more automatic approach. About import/search path I would also prefer if they could be set though a platform dependent fil

Re: [Development] Platform Content Selection

Having a release build with only the required files seems like a good idea, if one uses a search path based approach one can remove all non reachable duplicates, and then either store the used one again in the file system, or pack them in a QRC... Fawzi F

Re: [Development] Platform Content Selection

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 other files coming from a default location. Alan's solution looks very comprehen

Re: [Development] Qml mime types

nuary 08, 2013 5:16 PM To: Mohamed Fawzi Cc: development@qt-project.org Subject: Re: [Development] Qml mime types On 7 Jan 2013, at 11:21 AM, Mohamed Fawzi wrote: > I would like to close the discussion if possible. > Is the following hierarchy acceptable? > > text/plain; char

Re: [Development] QML Runtime

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 other as bigger. Even having a single binary does not remove a

Re: [Development] Qml mime types

and the hierarchy seems sane. Fawzi From: Koehne Kai Sent: Thursday, December 20, 2012 12:32 PM To: Mohamed Fawzi; Alan Alpert Cc: fa...@kde.org; development@qt-project.org; Knoll Lars Subject: RE: [Development] Qml mime types > Subject: Re: [Development] Qml mime types > > D

Re: [Development] Qml mime types

.qt.project+qml => .qmlproject files but I wonder how to define exactly the difference between text/vnd.qt.qml-base text/vnd.qt.qml, so I am not convinced of this second option Fawzi From: Alan Alpert [4163654...@gmail.com] Sent: Wednesday, December 12

Re: [Development] Qml mime types

t.org] on behalf of Marc Mutz [marc.m...@kdab.com] Sent: Thursday, December 13, 2012 1:19 AM To: development@qt-project.org Subject: Re: [Development] Qml mime types On Wednesday December 12 2012, Mohamed Fawzi wrote: > text/plain; charset=utf-8 >text/vnd.qt.qml-base : a file using the qm

Re: [Development] Qml mime types

kipped it, but I am willing to reconsider that if someone feels strongly about that. Fawzi From: Alan Alpert [4163654...@gmail.com] Sent: Tuesday, December 11, 2012 9:03 PM To: Mohamed Fawzi Cc: Knoll Lars; fa...@kde.org; development@qt-project.org Subject

Re: [Development] QML Singletons

I very much prefer the static keyword approach, as it does not depend on how the file is imported. Note that one could make even nested static declarations work if one sees them as static x in Type1 Type2=> add an instance of x identified with Type1Id.Type2Id.x (or the AST node of x, or the off

Re: [Development] Qml mime types

I like the +qml suffix. About the different file types you propose the problem is that you probably don't want to differentiate stuff that is different due to imports and plugins loaded, but uses the same basic architecture. Still maybe it is a good idea. Fawzi __

Re: [Development] Qml mime types

2012 14.12.12, Mohamed Fawzi wrote: > text/vnd.qt.qml-base > for the superclass of all files with qml syntax, and > text/vnd.qt.qml > for the qml runtime specific files > sound better? How is that any different? What's a "qml runtime"? -- Thiago Macieira -

Re: [Development] Convenience Imports in QML

A way to work around that problem is to have completion on the imports with version number. This is something I am currently working on in the qmljs editor of QtCreator. In the future one could even think about suggesting the import given what you use, but that is a more complex change. Fawzi __

Re: [Development] Qml mime types

specific files sound better? Any other proposal? Fawzi From: Knoll Lars Sent: Tuesday, December 11, 2012 2:01 PM To: Mohamed Fawzi Cc: development@qt-project.org; fa...@kde.org Subject: Re: [Development] Qml mime types On Dec 11, 2012, at 10:48 AM,

[Development] Qml mime types

Now Qt has several files that use the QML syntax: * .qml files of QtQuick 1 and QtQuick 2 * .qbs files * .qmlproject files * .qmltypes files I wanted to clean up a bit the mime types for the editor, and introduce q generic "QML syntax" file type. I began doing it using the current application/x