[Development] Summary of renaming changes

Koehne Kai Kai.Koehne at digia.com
Fri Oct 19 09:09:40 CEST 2012

> -----Original Message-----
> From: development-bounces+kai.koehne=digia.com at qt-project.org
> [mailto:development-bounces+kai.koehne=digia.com at qt-project.org] On
> Behalf Of Thiago Macieira
> Sent: Thursday, October 18, 2012 7:31 PM
> To: development at qt-project.org
> Subject: Re: [Development] Summary of renaming changes
> [...]
> So I'm going to recommend renaming qmlviewer and qmlplugindump back
> to the Qt
> 4 names and call them "applications". Distributions will not co-install both:
> one simply upgrades them and keeps *all* of the functionality.

Especially for qmlplugindump I don't agree. Its sole use right now is to get meta information about a QML plugin for Qt Creator code completion: It's either called internally from Qt Creator, or the plugin developer can also explicity dump the information to a .qmltypes file e.g. in the build process of the plugin. Now, experience shows people often rather live with broken code completion in Qt Creator compared to having any hassle with qmlplugindump, so asking them to always compile their plugins with latest Qt 5 just to get code completion won't work.

So, _if_ we already rename half of the tools I don't see why qmlplugindump + qmlviewer should be the exception. Same goes for qmlviewer. Designer is a bit different since I guess 90% of the people just use it with stock component sets ...



> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center

More information about the Development mailing list