Re: [Development] QML Tooling Renames (was: Pending decisions on co-installation)
To summarize QML tool naming discussion so far: In qtquick1 repo qmlviewer - qml1viewer qmlplugindump - qml1plugindump That's already the name, isn't it? In qtdeclarative repo qmlscene - qml2scene qmlplugindump - qml2plugindump qmlbundle - move to playground qmlmin - qmlmin qmlprofiler - qmlprofiler qmltestrunner - qml2testrunner qmleasing - qml2easing easingcurveeditor - qml2easing (merge tools) Does anyone have any further feedback on QML tool renaming before these get implemented? I don't feel too strong about the particular names anymore. But if you're changing the names of especially qmlplugindump, qmlviewer, qmlscene, it should go in fast ! We need to fix Qt Creator then, too, and I guess also a bunch of documentation ... I am quite against the renaming of binaries. Does qml2scene mean that there is an equivalent qml1scene? what is the difference between qmlviewer in qt 4.8 and qt 5.0 that a renaming is necessary? As for qmlplugindump, it is a special tool. Maybe creating a tool that dumps plugin info for both Qt Quick 1 and 2 is a good idea. ~Aurindam ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QML Profiler for Qt5.0-Beta1 programs
Some ways to do this: 1) If you can connect to the arm board via network, then * Start you application with -qmljsdebugger=port:port number * From QtCreator, connect to the applicationvia Attach to QML Profiler and specify the IP and the above port 2) You can use the standalone profiler in Qt-5. * qmlprofiler [options] [program] [program-options] This launches the app and starts profiling Options: -fromStart will start profiling as soon as the app is running Commands: r - toggle record etc * start application with -qmljsdebugger=port:port number Use qmlprofiler [options] -attach [hostname] to attach to the application. The profiled data will be stored in a user defined file which can then be read using QtCreator QML Profiler tool to generate graphs etc. -- Aurindam Jana, Software Engineer - Digia, Qt Don't Panic! Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius Registergericht: Amtsgericht Charlottenburg, HRB 144331 B On Oct 18, 2012, at 8:07 AM, Labs, Torsten wrote: Hi, I have a problem using QML Profiler with Qt5-Beta1 based programs. I use a QPA based architecture on a Arm board and will try to connect the QML Profiler with a Qt Creator 2.5.2. Is it possible? How can I do it? Do I hav do use another Qt Creator? Thanks. Torsten With best regards, Torsten Labs Siemens AG Industry Sector Industry Automation Division Industrial Automation Systems Factory Automation mailto:torsten.l...@siemens.com Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme; Managing Board: Peter Loescher, Chairman, President and Chief Executive Officer; Roland Busch, Brigitte Ederer, Klaus Helmrich, Joe Kaeser, Barbara Kux, Hermann Requardt, Siegfried Russwurm, Peter Y. Solmssen, Michael Suess; Registered offices: Berlin and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Summary of renaming changes
On Oct 18, 2012, at 5:30 PM, Thiago Macieira wrote: After all of my patches are integrated, here are the changes that will happen: - bin: The following tools have been renamed: qmake - qmake5 moc - moc5 uic - uic5 rcc - rcc5 qdbusxml2cpp - qdbusxml2cpp5 qdbuscpp2xml - qdbuscpp2xml5 lconvert - lconvert5 lrelease - lrelease5 lupdate - lupdate5 xmlpatterns - xmlpatterns5 xmlpatternsvalidator - xmlpatternsvalidator5 qmlviewer - qml1viewer This should be just qmlviewer (as it was in Qt 4.8).. I dont see a reason for this renaming.. [qml1plugindump had already been renamed] This should be reverted back to qmlplugindump .. (Same reason as above.. For QtQuick2, the related binaries can be renamed to qml2* (to reflect the version change) qmlscene - qml2scene This should be qml2viewer. qmlplugindump - qml2plugindump qmlbundle - qml2bundle qmlmin - qml2min qmlprofiler - qml2profiler qmltestrunner - qml2testrunner The following tools require more information: qdoc: not renamed because the Qt 4 version was called qdoc3 qhelpgenerator, qcollectiongenerator, qhelpconverter: they apparently keep backwards compatibility, so they should replace the Qt 4 versions qglinfo: new tool from qt3d The following are user applications and they have not and will not be renamed: qdbus qdbusviewer assistant designer linguist creator pixeltool - lib: All libraries are now called libQt5Name.so.5 on Unix systems, libQt5Name(_debug).5.dylib on Mac, Qt5Name(d).dll on Windows. This also applies to the qmake .prl files, the libtool .la files and the pkg-config .pc files. The cmake files had already had the 5. EXCEPT in Mac Framework builds. Since the header search path takes the framework's name, for source compatibility, the framework builds did not get the 5 in the name. - include: No change. - doc: On Windows builds and on -no-prefix-install builds, no change. Otherwise, the default install path is now $prefix/share/qt5/doc. Question: should it be $prefix/doc/qt5 to match autoconf's default? - mkspecs: On Windows builds, on -no-prefix-install builds, and on builds with -hostprefix, no change. Otherwise, the default install path is now $prefix/lib/qt5/mkspecs. - plugins: The default install path is now $prefix/lib/qt5/plugins on all systems. - imports: The default install path is now $prefix/lib/qt5/imports on all systems. It applies to QML 1 and Qt Quick 1 only. QML2 imports go to qmldir, which defaults to $prefix/lib/qt5/qml on all systems. -- Thiago Macieira - thiago.macieira (AT) intel.comhttp://intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.orgmailto:Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development -- Aurindam Jana, Software Engineer - Digia, Qt Don't Panic! Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
