[Development] Proposal: Rename Qt WebSockets QML import

Sze Howe Koh szehowe.koh at gmail.com
Sun Oct 5 02:23:13 CEST 2014


On 30 September 2014 20:56, Blasche Alexander
<Alexander.Blasche at digia.com> wrote:
>> -----Original Message-----
>> From: development-bounces+alexander.blasche=digia.com at qt-project.org
>> [mailto:development-bounces+alexander.blasche=digia.com at qt-project.org]
>> On Behalf Of Sze Howe Koh
>
>> To bring the WebSocket QML import name in line with other modules
>> (e.g. "QtWebEngine 1.0", "QtQuick 2.x", "QtWebKit 3.x", "QtSensors
>> 5.x"), I propose changing the import:
>>
>> - From "import Qt.WebSockets 1.0"
>> - To "import QtWebSockets 1.1" (no dot between "Qt" and "WebSockets")
>
> I was considering to do the same a couple of days ago when I fixed the docs for it. If/when you do this please don't forgot to update the docs too.

Ok, there have been no objections so here is my first attempt:

    https://codereview.qt-project.org/#/c/96406/


> However why bumping the version?  It would be just a rename while retaining the old name.
>
> If you must bump it it should rather be a bump it to 5.x. This forest of versions is just confusion without no purpose.

I considered bumping the version because the rename is a significant
change, but I've left it as-is now.

I'm not a fan of the potpourri of version numbers myself, but I think
that's best left for a separate discussion.


>> Ideally, the old import name + version number would still be available
>> for compatibility, while newer versions would use the new name. Is
>> this supported?
>
> Yes this can be done. It's just a matter of testing for both strings in the plug-ins type registrations.

Thanks. My current solution is to have a qmldir file in the old
location that points to the plugin in the new location. Unfortunately,
it also generates some dummy shared libraries when the module is
compiled (probably because my qmake-fu is not strong enough).

* Is there a way to copy the qmldir without building any binaries?
* Even better, is there a way to support the extra namespace without
having an extra qmldir file?


>> What does everyone think?
> +10 ;)

Regards,
Sze-Howe



More information about the Development mailing list