Re: [Development] Enumerations in QML

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't know when these issues will be > resolved, but the

Re: [Development] QML Runtime

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

Re: [Development] Settings API for QML

On Tue, Dec 11, 2012 at 5:46 AM, Thiago Macieira wrote: > On segunda-feira, 10 de dezembro de 2012 19.51.32, 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

Re: [Development] QML Runtime

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

Re: [Development] QML Runtime

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

Re: [Development] Question on QWS/QPA

Hi Samuel, Thanks for your reply. We would like to have only QtWebKit widget and not going to use QtQuick at this moment. So by default QPA/QWS client will render widgets on shared memory allocated via Qt and draws on it. Once done it request the QPA/QWS server to do the composition of widgets. Am

[Development] Application wide shortcuts API for QML

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 current QtQuick in both Qt 4.8 (1.1) and 5.0 (2.0). F

Re: [Development] QML Singletons

On Dec 11, 2012, at 4:55 AM, Alan Alpert <4163654...@gmail.com> wrote: > Qt 5 gains this great new qmlRegisterSingletonApi function for > exposing global functionality from C++. This is great but sometimes > you want to write that global functionality in QML instead of C++. Use > cases that come

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

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.so, libwindows.so, and libxcb.so respectively. The la

Re: [Development] Question on QWS/QPA

On 12/11/2012 09:53 AM, Arunprasad Rajkumar wrote: > Hi Samuel, > > Thanks for your reply. We would like to have only QtWebKit widget and > not going to use QtQuick at this moment. So by default QPA/QWS client > will render widgets on shared memory allocated via Qt and draws on it. > Once done it r

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

+1 from my side. Let's get that in today. Lars On Dec 11, 2012, at 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. > > Ho

Re: [Development] QML Singletons

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 keyword for that? static is already a reserved keyword in > Ecmascript 5.1, so we could maybe write single.qml as

Re: [Development] Convenience Imports in QML

Hi, On Tue, Dec 11, 2012 at 4:25 AM, Alan Alpert <4163654...@gmail.com> wrote: > import Qt 5.0 The moment I read this, I immediately had some reservations ... ... because of this: > What's the performance impact of importing a hundred types you don't > use? It's known to have a performance co

Re: [Development] QML Singletons

On Dec 11, 2012, at 10:18 AM, Thomas Hartmann wrote: > 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 keyword for that? static is already a reserved

Re: [Development] QML Singletons

On Tue, Dec 11, 2012 at 10:18 AM, Thomas Hartmann wrote: > 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 keyword for that? static is already a reserved >

Re: [Development] Question on QWS/QPA

Thanks Samuel. If possible point me some QWS guys :) On 11 December 2012 14:38, Samuel Rødal wrote: > On 12/11/2012 09:53 AM, Arunprasad Rajkumar wrote: > >> Hi Samuel, >> >> Thanks for your reply. We would like to have only QtWebKit widget and >> not going to use QtQuick at this moment. So by d

Re: [Development] QAction-like API for QML

On Tuesday, 2012-12-11, Alan Alpert wrote: > Action type: > QtObject { > property string text > property url imageSource > property string shortcut > property bool checkable: false > property bool checked: false > signal triggered(bool checked) > } > > Note that it has no-

Re: [Development] QML Runtime

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

[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

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

Thiago Macieira wrote: > On terça-feira, 11 de dezembro de 2012 01.06.56, Darryl Miles wrote: >> I think all of the other matters can be worked through except for the >> domain name issue and if that has to be changed (by renaming the >> project) then all the other other issues become moot. >> >> I

Re: [Development] QML Singletons

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 keyword for that? static is already a reserved >>> keyword in Ecma

Re: [Development] QML Runtime

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

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

On Tue, Dec 11, 2012 at 10:01:42AM +0100, Samuel Rødal wrote: > The static linking support currently assumed the latter, non-prefixed > library names, which means static linking is currently broken with any > of the other platform plugins. > it was already fixed. _

[Development] Foreign windows, embedding and transiency

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 QWindow could already offer most of it: == QWindow::QWindow(QWindow * parent) Creates a window a

Re: [Development] QAction-like API for QML

Op 11-12-2012 4:39, Alan Alpert schreef: > 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 toolbars and some other things. I think we'll need > something similar for QML, so that the QtQuic

Re: [Development] QAction-like API for QML

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 > enabled, visible or font

Re: [Development] QML Runtime

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

Re: [Development] Foreign windows, embedding and transiency

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 QWindow could already offer most > of it: > > == >

Re: [Development] QML Runtime

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 _

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

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] 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 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] 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: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] 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] 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 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] 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] 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] 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] 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] 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] 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 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] 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] 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] 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] 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] 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] 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] 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] 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 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] 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] 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] 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] [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] 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] 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] 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] 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] 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] 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] 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] 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] 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] 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] 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] 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] 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] 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

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

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

[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] 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. >>

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

  1   2   >