Re: [Development] QML Runtime

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 >>

Re: [Development] Qt Playground - Updating Daemon/Service Support

> > As I know others have expressed interest in helping out, here's the > bug report in case you want to join/watch: > > https://bugreports.qt-project.org/browse/QTQAINFRA-584 > > Ben > > > Does it usually take this long? I understand the RC is being released, > but it doesn't

Re: [Development] Enumerations in QML

Hi, I figured I weigh into this discussion: > But if you don't like those changes, you can do the var in a global > (.pragma library) script file and use that. Maybe this means proper > enum support isn't that urgent ;) . > It's not that the functionality is urgent; it's that currently, QML-doc

Re: [Development] Foreign windows, embedding and transiency

On Dec 11, 2012, at 1:30 PM, Alberto Mardegan wrote: > OK. Though I'd prefer to call it Qt::ForeignWindow, to make it obvious > that it's not owned by this process (Qt::NativeWindow just seems to tell > that the QWindow is associated with a native window, which is always > true, AFAIU). Yes,

Re: [Development] QML Runtime

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

Re: [Development] Qt Playground - Updating Daemon/Service Support

On Wed, Nov 28, 2012 at 11:11 AM, BRM wrote: > > From: BRM > > > Sent: Monday, November 26, 2012 9:39 PM > > Subject: Re: [Development] Qt Playground - Updating Daemon/Service > Support > >> From: Matt Broadstone > >> Subject: Re: [Development] Qt Playground - Updating Daemon/Service > Support

[Development] Re: Controlling QML Imports

On Tuesday, 11 December 2012 04:23:51 CEST, Alan Alpert wrote: > For finer-grained control over QML it would make sense to have an API > allowing import restrictions. Two usecases come to mind, platform > security contexts and scriptable applications. I'm currently using QML as a configuration lan

Re: [Development] Convenience Imports in QML

On 11/12/12 13:25, Alan Alpert wrote: > I've heard complaints about all the varying version numbers used in > QML imports. I don't think we can just standardize, for example on > 5.0, because the whole point of modularization is that modules don't > have to move in lockstep anymore. But I did hear

Re: [Development] Convenience Imports in QML

On 12/12/12 07:28, André Pönitz wrote: > What about something like > > import QtQml from Qt 5.0 > import QtQuick from Qt 5.0 +1 All the benefits of "a group of QML modules attached to a single Qt release" without the performance problem of pulling them all in. Then "Qt 5.0" is just some met

Re: [Development] Settings API for QML

On terça-feira, 11 de dezembro de 2012 15.55.52, Alan Alpert wrote: > Would you care to sketch out what your PersistentSettings element > would look like in practice? In a non QML approximant syntax: Rectangle { PersistentSettings { id: settings property int width path("applic

Re: [Development] QAction-like API for QML

On Tue, Dec 11, 2012 at 03:20:35PM -0800, Alan Alpert wrote: > On Tue, Dec 11, 2012 at 2:57 PM, André Pönitz > wrote: > > On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote: > > ... > > > >> But there are other ways to support those use cases than adding a > >> C++ API for the new Actions

Re: [Development] Settings API for QML

On Tue, Dec 11, 2012 at 3:30 PM, Thiago Macieira wrote: > On terça-feira, 11 de dezembro de 2012 15.10.18, Alan Alpert wrote: >> The two-way binding would be tricky. You don't have a reference to the >> property and I'd prefer this not be baked into the language. >> >> But here's another way of do

Re: [Development] Application wide shortcuts API for QML

On Tue, Dec 11, 2012 at 2:47 PM, Rick Stockton wrote: > > ... > > Alan, I can't think of _good_ ways to extend QKeySequence into the thing > I'd like. As you know, we've had problems (some difficult) with even the > most simple 2-character keyboard sequences. And Backward Compatibility > issues, w

Re: [Development] Settings API for QML

On terça-feira, 11 de dezembro de 2012 15.10.18, Alan Alpert wrote: > The two-way binding would be tricky. You don't have a reference to the > property and I'd prefer this not be baked into the language. > > But here's another way of doing roughly that: > Rectangle { > Persistent.property("widt

Re: [Development] Settings API for QML

On terça-feira, 11 de dezembro de 2012 14.51.31, Alan Alpert wrote: > The reason why most QML APIs are developed separate from C++ > considerations is that there's already a C++ API for that > functionality. For new functionality QML and C++ APIs should be > developed side-by-side where possible. E

Re: [Development] Application wide shortcuts API for QML

On Tue, Dec 11, 2012 at 1:11 PM, Mark wrote: > On Tue, Dec 11, 2012 at 9:50 PM, Alan Alpert <4163654...@gmail.com> wrote: >> On Tue, Dec 11, 2012 at 12:29 PM, Mark wrote: >>> On Tue, Dec 11, 2012 at 9:11 PM, Alan Alpert <4163654...@gmail.com> wrote: On Tue, Dec 11, 2012 at 10:56 AM, Mark wr

Re: [Development] QAction-like API for QML

On Tue, Dec 11, 2012 at 2:57 PM, André Pönitz wrote: > On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote: > ... > >> But there are other ways to support those use cases than adding a >> C++ API for the new Actions. My initial thought is something like a >> QActionBridge which can take a

Re: [Development] Settings API for QML

On Tue, Dec 11, 2012 at 11:09 AM, Thiago Macieira wrote: > On terça-feira, 11 de dezembro de 2012 16.40.50, Bache-Wiig Jens wrote: >> Rectangle { >> property int width: Qt.storedProperty("application.width", 400) >> property int height: Qt.storedProperty("application.height", 400) >> } > >

Re: [Development] QAction-like API for QML

On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote: > > > > We also need to find out whether we can come up with something which > > QtWidgets users can migrate to (the QWidget* in the QAction API is > > quite niche, and not necessarily ideal API anyway). Possibly even > > investigating wh

Re: [Development] Settings API for QML

On Tue, Dec 11, 2012 at 5:55 AM, Shawn Rutledge wrote: > On Mon, Dec 10, 2012 at 07:51:32PM -0800, Alan Alpert wrote: >> There was a discussion a while ago about a better settings API for >> QML, http://permalink.gmane.org/gmane.comp.lib.qt.qml/3162 was the >> best link I could find, but no progre

Re: [Development] Settings API for QML

On Tue, Dec 11, 2012 at 6:36 AM, Stephen Kelly wrote: > On Monday, December 10, 2012 20:46:19 Thiago Macieira wrote: >> Before we do settings for QML, we need to figure out what to replace >> QSettings with. Or, better yet, we do the two at the same time: we develop >> the new C++ and QML setting

Re: [Development] Application wide shortcuts API for QML

On 12/11/2012 12:11 PM, Alan Alpert wrote: > On Tue, Dec 11, 2012 at 10:56 AM, Mark wrote: >> >> That sounds awesome :) Qt 5.1 material i guess? > It gets in when it's ready. If it's quickly agreed to and easily > implemented, it could get into 5.1. > >>> ... >>> It wasn't explained well in the

Re: [Development] Application wide shortcuts API for QML

On Tue, Dec 11, 2012 at 11:28 PM, Shawn Rutledge wrote: > On 11 December 2012 22:11, Mark wrote: >> In my opinion it certainly needs to be separated. Here is my usecase >> why i think that way. >> Right now i'm building a file manager application in QML (it looks >> awesome and a lot like [1] tho

Re: [Development] Application wide shortcuts API for QML

On 11 December 2012 22:11, Mark wrote: > In my opinion it certainly needs to be separated. Here is my usecase > why i think that way. > Right now i'm building a file manager application in QML (it looks > awesome and a lot like [1] though less windows 8 like) In that > application i need to have s

Re: [Development] Controlling QML Imports

> From: Alan Alpert <4163654...@gmail.com> >Sent: Tuesday, December 11, 2012 2:46 PM >Subject: Re: [Development] Controlling QML Imports > >On Tue, Dec 11, 2012 at 7:52 AM, Thiago Macieira wrote: >> On terça-feira, 11 de dezembro de 2012 15.44.37, Aaron J. Seigo wrote: >>> > > > loading of nativ

Re: [Development] Convenience Imports in QML

On Mon, Dec 10, 2012 at 07:25:57PM -0800, Alan Alpert wrote: > I've heard complaints about all the varying version numbers used in > QML imports. I don't think we can just standardize, for example on > 5.0, because the whole point of modularization is that modules don't > have to move in lockstep a

Re: [Development] Application wide shortcuts API for QML

On Tue, Dec 11, 2012 at 9:50 PM, Alan Alpert <4163654...@gmail.com> wrote: > On Tue, Dec 11, 2012 at 12:29 PM, Mark wrote: >> On Tue, Dec 11, 2012 at 9:11 PM, Alan Alpert <4163654...@gmail.com> wrote: >>> On Tue, Dec 11, 2012 at 10:56 AM, Mark wrote: On Tue, Dec 11, 2012 at 5:12 PM, Alan Alp

Re: [Development] QAction-like API for QML

On Tue, Dec 11, 2012 at 10:49 AM, Shawn Rutledge wrote: > On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote: >> Why can't this be QML-only? For the set of controls exposed in >> C++-only we have a C++-only Action API. When we add a set of controls >> exposed in QML-only we can have a QML

Re: [Development] Application wide shortcuts API for QML

On Tue, Dec 11, 2012 at 12:29 PM, Mark wrote: > On Tue, Dec 11, 2012 at 9:11 PM, Alan Alpert <4163654...@gmail.com> wrote: >> On Tue, Dec 11, 2012 at 10:56 AM, Mark wrote: >>> On Tue, Dec 11, 2012 at 5:12 PM, Alan Alpert <4163654...@gmail.com> wrote: On Tue, Dec 11, 2012 at 12:53 AM, Mark w

Re: [Development] Application wide shortcuts API for QML

On Tue, Dec 11, 2012 at 9:11 PM, Alan Alpert <4163654...@gmail.com> wrote: > On Tue, Dec 11, 2012 at 10:56 AM, Mark wrote: >> On Tue, Dec 11, 2012 at 5:12 PM, Alan Alpert <4163654...@gmail.com> wrote: >>> On Tue, Dec 11, 2012 at 12:53 AM, Mark wrote: Hi, Alan' posts about possible

Re: [Development] Application wide shortcuts API for QML

On Tue, Dec 11, 2012 at 10:56 AM, Mark wrote: > On Tue, Dec 11, 2012 at 5:12 PM, Alan Alpert <4163654...@gmail.com> wrote: >> On Tue, Dec 11, 2012 at 12:53 AM, Mark wrote: >>> Hi, >>> >>> Alan' posts about possible future APIs made me want to post this as >>> well. In the QWidget works we have th

Re: [Development] Application wide shortcuts API for QML

On Tue, Dec 11, 2012 at 8:46 PM, Mark wrote: > On Tue, Dec 11, 2012 at 8:04 PM, Rick Stockton > wrote: >> On 12/11/2012 12:53 AM, Mark wrote: >>> Hi, >>> >>> Alan' posts about possible future APIs made me want to post this as >>> well. In the QWidget works we have the rather nice QShortcut class

Re: [Development] Qml mime types

On Tue, Dec 11, 2012 at 6:12 AM, Mohamed Fawzi wrote: > I sort of expected qml-qt-quick to be considered not ok (also Marco Bubke > raised that point), which is a fair point, considering BB for example. > I am open to better naming, still I would like to differentiate > "file using qml syntax"

Re: [Development] Controlling QML Imports

On Tue, Dec 11, 2012 at 7:52 AM, Thiago Macieira wrote: > On terça-feira, 11 de dezembro de 2012 15.44.37, Aaron J. Seigo wrote: >> > > > loading of native plugins from the application? >> >> Yes, but not native plugins installed by the QML applications. In such a >> situation we need to be able t

Re: [Development] Application wide shortcuts API for QML

On Tue, Dec 11, 2012 at 8:04 PM, Rick Stockton wrote: > On 12/11/2012 12:53 AM, Mark wrote: >> Hi, >> >> Alan' posts about possible future APIs made me want to post this as >> well. In the QWidget works we have the rather nice QShortcut class to >> aid us in defining application wide shortcuts. >>

[Development] Cleaning up the P1 tasks

Hello We want to release RC2 tomorrow and we are quite confident of having zero P0s left. However, there are some 40 tasks with P1 priority that need attention. P1 means "Showstopper", so anything P1 for 5.0.0 should stop the release. In the next 24 hours, I'd like the following: - everyone w

Re: [Development] QML Runtime

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

Re: [Development] QML Runtime

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

Re: [Development] QML Runtime

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

Re: [Development] Enumerations in QML

On Tue, Dec 11, 2012 at 12:26 AM, Mark wrote: > On Tue, Dec 11, 2012 at 4:47 AM, Alan Alpert <4163654...@gmail.com> wrote: >> People keep asking for enumerations in QML. See QTBUG-15483 and >> QTBUG-14861, both assigned to old Nokia identities (so don't trust >> that 'in progress' ;) ). Now I don'

Re: [Development] Settings API for QML

On terça-feira, 11 de dezembro de 2012 16.40.50, Bache-Wiig Jens wrote: > Rectangle { > property int width: Qt.storedProperty("application.width", 400) > property int height: Qt.storedProperty("application.height", 400) > } Will this bind the stored property back to the width? I.e., two-wa

Re: [Development] QML Runtime

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

Re: [Development] Application wide shortcuts API for QML

On 12/11/2012 12:53 AM, Mark wrote: > Hi, > > Alan' posts about possible future APIs made me want to post this as > well. In the QWidget works we have the rather nice QShortcut class to > aid us in defining application wide shortcuts. > > Functionality like that is completely missing from the curre

Re: [Development] Enumerations in QML

On Tue, Dec 11, 2012 at 5:17 AM, Knoll Lars wrote: > > On Dec 11, 2012, at 4:47 AM, Alan Alpert <4163654...@gmail.com> wrote: > >> People keep asking for enumerations in QML. See QTBUG-15483 and >> QTBUG-14861, both assigned to old Nokia identities (so don't trust >> that 'in progress' ;) ). Now I

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] Application wide shortcuts API for QML

On Tue, Dec 11, 2012 at 5:12 PM, Alan Alpert <4163654...@gmail.com> wrote: > On Tue, Dec 11, 2012 at 12:53 AM, Mark wrote: >> Hi, >> >> Alan' posts about possible future APIs made me want to post this as >> well. In the QWidget works we have the rather nice QShortcut class to >> aid us in defining

Re: [Development] QAction-like API for QML

On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote: > Why can't this be QML-only? For the set of controls exposed in > C++-only we have a C++-only Action API. When we add a set of controls > exposed in QML-only we can have a QML-only Action API. We don't Because it seems likely that the b

Re: [Development] QtQml Loader API

On Mon, Dec 10, 2012 at 8:15 PM, Martin Jones wrote: > On Tue, Dec 11, 2012 at 1:32 PM, Alan Alpert <4163654...@gmail.com> wrote: >> Finally Qt 5 brings better QtQml and QtQuick separation! Better, not >> perfect. The main things I've heard are missing is dynamic >> instantiation of non-Items. Wha

Re: [Development] QAction-like API for QML

Tirsdag 11. desember 2012 09.25.37 skrev Alan Alpert: > On Tue, Dec 11, 2012 at 5:12 AM, Stephen Kelly wrote: > > Hi Alan, > > > > Thanks for your initiative in pointing out what is still missing in > > QtQml/QtQuick. > > > > On Monday, December 10, 2012 19:39:36 Alan Alpert wrote: > >> Note th

Re: [Development] Convenience Imports in QML

> > > I understand others' concerns about "load-performance". , > The concern about load-performance isn't about "users now have an > informed choice between faster development speed or faster runtime > speed". The concern is about people using import Qt 5.0 because it's > convenient, and then

Re: [Development] Convenience Imports in QML

On Tue, Dec 11, 2012 at 8:44 AM, Charley Bay wrote: > Alan spaketh: > I've heard complaints about all the varying version numbers used in >> >> QML imports. I don't think we can just standardize, for example on >> 5.0, because the whole point of modularization is that modules don't >> have to move

Re: [Development] QAction-like API for QML

On Tue, Dec 11, 2012 at 6:07 AM, Stephen Kelly wrote: > On Monday, December 10, 2012 19:39:36 Alan Alpert wrote: >> Here's a hypothetical example of how it could work >> in practice. >> >> MenuControl { >> //Default property is property list actions >> ActionGroup { >> id: fileActi

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

this would allow cascade based stuff to use the same text/vnd.qt.qml type as the qt-quick one without it sounding strange, as the file type does not refer qt-quick. Please not that I am not sure that this is the correct way to approach this, as I like that files that have to be handled differen

Re: [Development] QAction-like API for QML

On Tue, Dec 11, 2012 at 5:12 AM, Stephen Kelly wrote: > > Hi Alan, > > Thanks for your initiative in pointing out what is still missing in > QtQml/QtQuick. > > On Monday, December 10, 2012 19:39:36 Alan Alpert wrote: >> Note that it has no-where near as many properties as QAction. toolTip >> and w

Re: [Development] QAction-like API for QML

On Mon, Dec 10, 2012 at 9:05 PM, Martin Jones wrote: > On Tue, Dec 11, 2012 at 1:39 PM, Alan Alpert <4163654...@gmail.com> wrote: >> QAction served widgets well as an abstraction for an "Action" which is >> exposed to the UI in a platform specific manner. This was shared >> between menus and toolb

Re: [Development] Convenience Imports in QML

Alan spaketh: I've heard complaints about all the varying version numbers used in > QML imports. I don't think we can just standardize, for example on > 5.0, because the whole point of modularization is that modules don't > have to move in lockstep anymore. But I did hear an idea at Dev Days > to

Re: [Development] Settings API for QML

>> I would also consider an even simpler API. How about we introduce a new >> keyword for persistent properties and make it part of the language. >> >> Rectangle { >> id: root >> persistent property width: 400 >> persistent property height: 300 >> } >> >> What this means is that the

Re: [Development] Convenience Imports in QML

On Tue, Dec 11, 2012 at 6:29 AM, Mohamed Fawzi wrote: > 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 gi

Re: [Development] QML Singletons

On Tue, Dec 11, 2012 at 1:52 AM, Thomas Hartmann wrote: > Am 11/12/2012 10:23, schrieb Knoll Lars: > > Hi, > > it's a bit weird that you need a qmldir for that. Wouldn't it be better if we could mark this as singleton in the implementation (ie. inside single.qml)? Maybe use a new

Re: [Development] Qml mime types

On Tuesday December 11 2012, Marc Mutz wrote: >   text/vnd.qt.quick+qml >   text/vnd.rim.cascades+qml (assuming that's what you meant with BB above) or +vnd.t.qml, just to be extra paranoid in case W3C develops a Quantum Modelling Language anytime soon and finds their suffix gone. -- Marc Mutz

Re: [Development] Settings API for QML

Op 11-12-2012 16:37, Bache-Wiig Jens schreef: >> To get the discussion going, here's my suggestion for that API: >> PersistentSettings >> { >> property bool loadOnStartup: true >> property bool saveOnExit: true >> function load() >> function save() >> } > I would also consider an ev

Re: [Development] Application wide shortcuts API for QML

On Tue, Dec 11, 2012 at 12:53 AM, Mark wrote: > Hi, > > Alan' posts about possible future APIs made me want to post this as > well. In the QWidget works we have the rather nice QShortcut class to > aid us in defining application wide shortcuts. > > Functionality like that is completely missing fro

Re: [Development] Qml mime types

On Tuesday December 11 2012, Mohamed Fawzi wrote: > would >   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? For XML, which has the same problem exponentiated, IETF introduced the +xml suffix, to

Re: [Development] Qml mime types

On terça-feira, 11 de dezembro de 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 - th

Re: [Development] Settings API for QML

On Tue, Dec 11, 2012 at 03:37:23PM +, Bache-Wiig Jens wrote: > I would also consider an even simpler API. How about we introduce a new > keyword for persistent properties and make it part of the language. > > Rectangle { > id: root > persistent property width: 400 > persistent pro

Re: [Development] Settings API for QML

On terça-feira, 11 de dezembro de 2012 09.41.48, Mark wrote: > Perhaps it's an idea to look at KConfig for Qt inclusion? KConfig (XT) > seems nice and works rather well in KDE applications. All that's > needed then is a QML API to access the KConfig configuration. If i'm > right, KDE already has th

Re: [Development] QML Runtime

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

Re: [Development] Controlling QML Imports

On terça-feira, 11 de dezembro de 2012 15.44.37, Aaron J. Seigo wrote: > > > > loading of native plugins from the application? > > Yes, but not native plugins installed by the QML applications. In such a > situation we need to be able to ensure that applications which say "I will > access this list

Re: [Development] Enumerations in QML

> > > People keep asking for enumerations in QML. , > > Now I don't know when these issues will be > > resolved, but there's an important discussion to have before it can > > even be scheduled: What would proper enum support look like in QML? > > , > > I'd prefer: > > Item { > enum Wea

Re: [Development] qt-jambi-inter...@qt.nokia.com

On terça-feira, 11 de dezembro de 2012 09.50.19, Darryl Miles wrote: > Thiago Macieira wrote: > > I think you're confusing again the Qt Project with Digia. > > You had stated the "Qt Project legal team" consists of one person in the > legal department at Digia. > > So in corresponding with this per

Re: [Development] [Interest] [ANN] Registration for C++Now 2013 is now open

On terça-feira, 11 de dezembro de 2012 13.14.00, Boris Kolpackov wrote: > Speakers > > If you are interested in presenting, we are currently accepting proposals > . Registration fee is waived > for one speaker of every standard session presentation. Sho

Re: [Development] Settings API for QML

> > To get the discussion going, here's my suggestion for that API: > PersistentSettings > { >property bool loadOnStartup: true >property bool saveOnExit: true >function load() >function save() > } I would also consider an even simpler API. How about we introduce a new keyword fo

Re: [Development] QtQml Loader API

Alan spaketh: > Finally Qt 5 brings better QtQml and QtQuick separation! Better, not perfect. The main things I've heard are missing is dynamic > instantiation of non-Items. What I propose is a new element for the > QtQml module which provides that functionality. Note that while some > people ha

Re: [Development] Making sure all platform plugin library names are prefixed with "q"

On 12/11/2012 10:01 AM, Samuel Rødal wrote: > Hello, > > currently the platform plugin library name is a bit inconsistent. In > most cases it will have the "q" prefix, for instance libqeglfs.so, > libqminimal.so, libqcocoa.so, etc. > > However, the qnx, windows, and xcb libraries were named libqnx.

Re: [Development] Qml mime types

On Dec 11, 2012, at 3:12 PM, Mohamed Fawzi wrote: > I sort of expected qml-qt-quick to be considered not ok (also Marco Bubke > raised that point), which is a fair point, considering BB for example. > I am open to better naming, still I would like to differentiate > "file using qml syntax" > f

Re: [Development] Controlling QML Imports

(sorry for interjecting a reply to multiple emails here, but i just got back on this list specifically to discuss QML matters.) On Tuesday, December 11, 2012 14:21:28 Laszlo Papp wrote: > On Tue, Dec 11, 2012 at 1:11 PM, Knoll Lars wrote: > > On Dec 11, 2012, at 5:30 AM, Thiago Macieira > > > c

Re: [Development] QML Runtime

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

Re: [Development] Settings API for QML

On Monday, December 10, 2012 20:46:19 Thiago Macieira wrote: > Before we do settings for QML, we need to figure out what to replace > QSettings with. Or, better yet, we do the two at the same time: we develop > the new C++ and QML settings APIs at the same time. I agree with this, of course. QML

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] QAction-like API for QML

On Tue, Dec 11, 2012 at 11:39:26AM +, Davet Jacques wrote: > Shawn Rutledge : > > On Mon, Dec 10, 2012 at 07:39:36PM -0800, Alan Alpert wrote: > >> Note that it has no-where near as many properties as QAction. toolTip > >> and whatsThis for example are very desktop centric so not needed > >> an

Re: [Development] Controlling QML Imports

On Tue, Dec 11, 2012 at 1:11 PM, Knoll Lars wrote: > > On Dec 11, 2012, at 5:30 AM, Thiago Macieira > wrote: > > > On terça-feira, 11 de dezembro de 2012 13.43.08, Lincoln Ramsay wrote: > >> On 11/12/12 13:23, Alan Alpert wrote: > >>> Any comments on adding an API like this? > >>> > >>> Are ther

Re: [Development] Qml mime types

I sort of expected qml-qt-quick to be considered not ok (also Marco Bubke raised that point), which is a fair point, considering BB for example. I am open to better naming, still I would like to differentiate "file using qml syntax" from ".qml file that is supposed to be loaded in the qml runt

Re: [Development] QAction-like API for QML

On Monday, December 10, 2012 19:39:36 Alan Alpert wrote: > Here's a hypothetical example of how it could work > in practice. > > MenuControl { > //Default property is property list actions > ActionGroup { > id: fileActions > text: "File" > collapsible: true >

Re: [Development] Settings API for QML

On Tue, Dec 11, 2012 at 01:37:53PM +, Knoll Lars wrote: > One idea we had earlier was to use JSON to load and save settings. The > advantage would be that it's JS compatible, and we could possibly even load > it in a way that you can simply bind to setting values in there. That would be hand

Re: [Development] Settings API for QML

On Mon, Dec 10, 2012 at 07:51:32PM -0800, Alan Alpert wrote: > There was a discussion a while ago about a better settings API for > QML, http://permalink.gmane.org/gmane.comp.lib.qt.qml/3162 was the > best link I could find, but no progress has been made since. The main > concensus I got from that

Re: [Development] Settings API for QML

On Dec 11, 2012, at 4:51 AM, Alan Alpert <4163654...@gmail.com> wrote: > There was a discussion a while ago about a better settings API for > QML, http://permalink.gmane.org/gmane.comp.lib.qt.qml/3162 was the > best link I could find, but no progress has been made since. The main > concensus I go

Re: [Development] Enumerations in QML

On Dec 11, 2012, at 4:47 AM, Alan Alpert <4163654...@gmail.com> wrote: > People keep asking for enumerations in QML. See QTBUG-15483 and > QTBUG-14861, both assigned to old Nokia identities (so don't trust > that 'in progress' ;) ). Now I don't know when these issues will be > resolved, but there

Re: [Development] QAction-like API for QML

Hi Alan, Thanks for your initiative in pointing out what is still missing in QtQml/QtQuick. On Monday, December 10, 2012 19:39:36 Alan Alpert wrote: > Note that it has no-where near as many properties as QAction. toolTip > and whatsThis for example are very desktop centric so not needed > anymo

Re: [Development] Controlling QML Imports

On Dec 11, 2012, at 5:30 AM, Thiago Macieira wrote: > On terça-feira, 11 de dezembro de 2012 13.43.08, Lincoln Ramsay wrote: >> On 11/12/12 13:23, Alan Alpert wrote: >>> Any comments on adding an API like this? >>> >>> Are there any other usecases which this might need to support? >> >> If we'

Re: [Development] Foreign windows, embedding and transiency

On 12/11/2012 01:30 PM, Alberto Mardegan wrote: > On 12/11/2012 12:47 PM, Sorvig Morten wrote: >> I've been planning this a bit from he perspective if the Cocoa port, here's >> what I think I need: >> >> - A Qt::WindowFlags flag ("Qt::NativeWindow") > > OK. Though I'd prefer to call it Qt::Foreign

Re: [Development] Qml mime types

On Dec 11, 2012, at 10:48 AM, Mohamed Fawzi wrote: > 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 "

Re: [Development] QML Runtime

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

Re: [Development] QML Runtime

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

Re: [Development] Foreign windows, embedding and transiency

On 12/11/2012 12:47 PM, Sorvig Morten wrote: > I've been planning this a bit from he perspective if the Cocoa port, here's > what I think I need: > > - A Qt::WindowFlags flag ("Qt::NativeWindow") OK. Though I'd prefer to call it Qt::ForeignWindow, to make it obvious that it's not owned by this p

Re: [Development] Editing the FAQs at qt-project.org/faq

On 05.12.2012 20:37, André Pönitz wrote: > I also don't think that establishing a system in parallel to the existing > Approver/Maintainers system is the best way to proceed. I actually doubt a > lot of maintainers want to become mad, scientifically or not, just to be > able to fix FAQ entries rela

Re: [Development] Foreign windows, embedding and transiency

On 12/11/2012 12:45 PM, Sletta Gunnar wrote: > > On Dec 11, 2012, at 12:33 PM, Samuel Rødal > wrote: > >> On 12/11/2012 12:03 PM, Alberto Mardegan wrote: >>> Hi all, >>> while digging a bit more deeply into the code of QX11EmbedWidget (in >>> order to port it to Qt5), I started wondering if

Re: [Development] Foreign windows, embedding and transiency

On Dec 11, 2012, at 12:33 PM, Samuel Rødal wrote: >> >> In order to create a QWindow for a foreign window, there might be a >> special subclass of QWindow (QForeignWindow?) or maybe it could just be >> a QWindow with a special Qt::ForeignWindow flag (and maybe a constructor >> like QWindow::QWin

Re: [Development] Foreign windows, embedding and transiency

On Dec 11, 2012, at 12:33 PM, Samuel Rødal wrote: > On 12/11/2012 12:03 PM, Alberto Mardegan wrote: >> Hi all, >>while digging a bit more deeply into the code of QX11EmbedWidget (in >> order to port it to Qt5), I started wondering if we really need a >> special API for embedding, or whether

Re: [Development] QAction-like API for QML

Shawn Rutledge : > On Mon, Dec 10, 2012 at 07:39:36PM -0800, Alan Alpert wrote: >> Note that it has no-where near as many properties as QAction. toolTip >> and whatsThis for example are very desktop centric so not needed >> anymore. Because it's not actually doing the rendering it doesn't need >> e

  1   2   >