Re: [Development] qdoc for C++ and QML

2017-04-24 Thread Uwe Rathmann
On Mon, 24 Apr 2017 17:09:43 +, Martin Smith wrote: > It doesn't need a separate comment, just something in the one common > comment that indicates the class is both C++ and QML. Most of the decisions about what parts of the APIs have to go to the QML docs can indeed be made without any

Re: [Development] QList

2017-04-24 Thread André Somers
Op 24/04/2017 om 20:39 schreef Marc Mutz: > On 2017-04-24 20:19, Ville Voutilainen wrote: > [...] >> What is wrong with QArrayList? > > Nothing, IMO, in the version proposed by me: > https://codereview.qt-project.org/188938 > > But since there's been no +2 forthcoming on above change, and I will

Re: [Development] QList

2017-04-24 Thread Marc Mutz
On 2017-04-24 20:19, Ville Voutilainen wrote: [...] What is wrong with QArrayList? Nothing, IMO, in the version proposed by me: https://codereview.qt-project.org/188938 But since there's been no +2 forthcoming on above change, and I will have no part in the massive code duplication that

Re: [Development] QList

2017-04-24 Thread Ville Voutilainen
On 24 April 2017 at 21:15, Marc Mutz wrote: > On 2017-04-06 09:20, Ville Voutilainen wrote: > [...] >> >> Okay, I will do it. :) > > [...] > > Interested to see the result, as I'm considering abandoning the QArrayList > changes. I'll try to get it done before the end of the

Re: [Development] QList

2017-04-24 Thread Marc Mutz
On 2017-04-06 09:20, Ville Voutilainen wrote: [...] Okay, I will do it. :) [...] Interested to see the result, as I'm considering abandoning the QArrayList changes. Thanks, Marc ___ Development mailing list Development@qt-project.org

Re: [Development] qdoc for C++ and QML

2017-04-24 Thread Martin Smith
>Not sure if qdoc is intended to be useful for 3rd party libraries as >well, but at least for my use case it would save me a lot of work. It is meant to be useful for 3rd party libraries, so we just need to agree on the right way to do this. From:

Re: [Development] qdoc for C++ and QML

2017-04-24 Thread Martin Smith
>Maybe qdoc could look for qmlRegisterType etc. in the cpp files and discover >those relationships without writing anything else? It has a better parser >these >days, right? It certainly does have a better parser, but for speed, we tell it not to parse the code blocks. Only declarations and

Re: [Development] qdoc for C++ and QML

2017-04-24 Thread Uwe Rathmann
On Mon, 24 Apr 2017 15:08:25 +, Shawn Rutledge wrote: > I guess we haven’t run into this very frequently yet because so few > classes have both a C++ and a QML API within the same class. Well, this is exactly my use case. All my controls are 100% implemented in C++ offering a full featured

Re: [Development] qdoc for C++ and QML

2017-04-24 Thread Shawn Rutledge
> On 24 Apr 2017, at 16:38, Martin Smith wrote: > > The problem when combining C++ and QML documentation is qdoc has no way of > knowing whether a QML type exists for a C++ class or whether a C++ class > exists for a QML type. > > Should we add a new command like \cpp-qml

Re: [Development] qdoc for C++ and QML

2017-04-24 Thread Martin Smith
The problem when combining C++ and QML documentation is qdoc has no way of knowing whether a QML type exists for a C++ class or whether a C++ class exists for a QML type. Should we add a new command like \cpp-qml to indicate that both exist and are documented the same? And if a C++ class has

Re: [Development] Exposing QMimeDatabase to QML; QtQml.Utils?

2017-04-24 Thread Edward Welbourne
Robin Burchell (24 April 2017 16:01) > I'd generally like to avoid a "Utils" import, since in my opinion they > far too easily end up as a dumping ground +1, also for anything with "misc" in its name. Such names are a red flag about bad modularisation, Eddy.

Re: [Development] qdoc for C++ and QML

2017-04-24 Thread Sean Harmer
Hi, On 24/04/2017 14:23, Martin Smith wrote: Regarding documenting both C++ and QML at the same time, I will be happy to implement it if we can get a good idea for how to do it. Well, take https://codereview.qt-project.org/#/c/192093/ as a case in point. The docs for the QML and C++ parts

Re: [Development] qdoc for C++ and QML

2017-04-24 Thread Sean Harmer
On 24/04/2017 14:26, Friedemann Kleint wrote: Hi, For starters, take a look at the script: http://code.qt.io/cgit/qt-creator/qt-creator.git/tree/scripts/qdoc2tasks.pl?h=4.3 You can pipe the error output of qdoc through it to convert it to a Qt Creator task file. Opening it in Qt Creator

Re: [Development] qdoc for C++ and QML

2017-04-24 Thread Friedemann Kleint
Hi, For starters, take a look at the script: http://code.qt.io/cgit/qt-creator/qt-creator.git/tree/scripts/qdoc2tasks.pl?h=4.3 You can pipe the error output of qdoc through it to convert it to a Qt Creator task file. Opening it in Qt Creator will show the issues as build issues (see

Re: [Development] qdoc for C++ and QML

2017-04-24 Thread Martin Smith
Regarding documenting both C++ and QML at the same time, I will be happy to implement it if we can get a good idea for how to do it. Regarding the creator issue, I don't understand the problem so I can't comment. martin From: Development

[Development] qdoc for C++ and QML

2017-04-24 Thread Sean Harmer
Hi, are there any plans to reduce/remove the redundancy when writing documentation for both C++ and QML? Seems a waste of time to have to copy/paste or update the docs twice for both languages when really the only things differing are the "Q" prefix on the class names in C++. On a related

Re: [Development] Exposing QMimeDatabase to QML; QtQml.Utils?

2017-04-24 Thread J-P Nurmi
On Mon, 2017-04-24 at 15:25 +0300, Alberto Mardegan wrote: > Hi all, >   in addition to making QMimeType usable from QML [1], jpnurmi also > suggested of exposing QMimeDatabase as a singleton. > > The open question is where this element should be added: I suggested > QtQtml.Models, given that

[Development] Exposing QMimeDatabase to QML; QtQml.Utils?

2017-04-24 Thread Alberto Mardegan
Hi all, in addition to making QMimeType usable from QML [1], jpnurmi also suggested of exposing QMimeDatabase as a singleton. The open question is where this element should be added: I suggested QtQtml.Models, given that it's a database, but maybe creating a separate module QtQml.Utils might be

Re: [Development] Qt 5.9 beta2 available

2017-04-24 Thread Eike Ziller
> On Apr 24, 2017, at 13:45, Martin Koller wrote: > > On Freitag, 21. April 2017 09:08:00 CEST Jani Heikkinen wrote: >> Hi all, >> >> Qt 5.9 beta2 is now available. Instructions how to get the release are here: >> https://wiki.qt.io/How_to_get_snapshot_via_online_installer.

Re: [Development] Qt 5.9 beta2 available

2017-04-24 Thread Martin Koller
On Freitag, 21. April 2017 09:08:00 CEST Jani Heikkinen wrote: > Hi all, > > Qt 5.9 beta2 is now available. Instructions how to get the release are here: > https://wiki.qt.io/How_to_get_snapshot_via_online_installer. Diff to first > beta can be found as an attachment. > > Please test the