[Development] PROPOSAL: merge #qt-qml and #qt-components to #qt-quick
Nurmi J-P
jpnurmi at digia.com
Mon Jul 1 16:04:38 CEST 2013
Hi again,
A new #qt-quick channel was established a couple of weeks ago, and the users of the former #qt-components were redirected to #qt-quick. Now that the dust has settled, I'd like to propose taking the next step - to merge #qt-qml to #qt-quick.
Users are increasingly confused by the separation between the two channels, and the questions seem to be pretty mixed too. Therefore I'm still voting for having a single #qt-quick channel for Qt Quick and QML users. Time will tell whether development discussions should be kept there or not.
--
J-P Nurmi
On Jun 11, 2013, at 7:11 PM, Alan Alpert <416365416c at gmail.com> wrote:
> I like the idea. For the average user, I definitely think #qt-quick is
> a better name. It has a much clearer association, due to users
> importing QtQuick and QtQuick.Controls in every file. And non-quick
> QML users won't get lost as badly (I once saw a Cascades user in
> #qt-qml, and no-one could help him :( . #qt-qnx is a better channel
> for Cascades-QML - now that QBS is 1.0.0 we don't want QBS users to
> get lost either).
>
> I would like to have a separate #qt-qml channel for the language
> issues (which are more working on the language than working with
> anyways), but that's not realistic because users can't always tell the
> difference. So maybe once the new #qt-quick channel is fully
> established and #qt-qml is empty, we can reclaim it. Or the
> language/engine development channel can have a more technical name to
> hide it from the average user. That second channel is less important,
> so it can wait for a later discussion, and QML language development
> chat can always go to #qt-labs until then.
>
> --
> Alan Alpert
>
>> On Jun 11, 2013, at 2:15 PM, Laszlo Papp <lpapp at kde.org> wrote:
>>
>>> Why not #qt-qml for the merged channel? I use the term "QML" more than "QtQuick" in this context.
>>>
>>> I agree about having one channel though.
>>>
>>>
>>> On Tue, Jun 11, 2013 at 3:04 PM, Nurmi J-P <jpnurmi at digia.com> wrote:
>>> Hi all,
>>>
>>> I'd like to propose merging the current #qt-qml and #qt-components IRC channels to a single channel called #qt-quick.
>>>
>>> Reasons:
>>> - the #qt-components name is outdated now that we have QtQuick Controls
>>> - most users don't understand the distinction between QML, QtQuick and QtQuick Controls.
>>>
>>> I believe this would make it easier for new users to find the correct channel. We would also setup automatic redirects from the old channels so the naming would be more or less transparent to the current users. Thoughts?
>>>
>>> --
>>> J-P Nurmi
>>>
>>> _______________________________________________
>>> Development mailing list
>>> Development at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/development
>>>
>>
>>
>> _______________________________________________
>> Development mailing list
>> Development at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
More information about the Development
mailing list