[Development] QtQuick ML

[Alan Alpert]

On Tue, Aug 27, 2013 at 12:46 PM, André Pönitz
<andre.poenitz at mathematik.tu-chemnitz.de> wrote:
> On Tue, Aug 27, 2013 at 03:48:18PM +0200, Juergen Bocklage-Ryannel wrote:
>> On 24.07.13 5:41 PM, Alan Alpert wrote:
>> > Since I can't seem to get them to speak up, I guess they don't care
>> > that much after all. I'll withdraw the suggestion again.
>> >
>> > See you in six months :P
>> >
>> Sorry haven't seen this thread. I'm working in several customer projects
>> now using purely QML/JS. Some other developers do the C++ parts. When we
>> work with customers we have a similar split: Frontend Developers do the
>> QML/JS code and Backend Developers do the C++ code. We work with
>> frontend developers who don't have a great understanding of C++ and also
>> are not interested in it. They are interested into ui elements /
>> animations / javascript / concepts / recipies, etc... A mailing list
>> where people speak about Qt/C++ mixed with some QML/JS would just
>> confuse them.
>
> Those frontend developers are surely not overly interested in the
> _development of Qt_, more of it's use, for which there's already
> interest at qt-project.org.
>
>> I think there is a great need to have an open forum / mailing list for
>> QML/JS users. Not sure if a Qt mailinglist is the right place for
>> people, but better than a mixed mailing list.
>
> Maybe for _users_ of QML and JavaScript. And if so, this should be clear
> in the naming of the list, e.g. by calling it qtquick-users at project.org.

André is correct that it's a separate issue, but it sounds like one
worth pursuing. +1 from me on the creation of a
qml-interest at qt-project.org list to match the C++ (and hybrid
use-case) qt-interest list.

As for forum, it already exists:
http://qt-project.org/forums/viewforum/12/ . But MLs and forums
attract different sorts of people, so I think there's value in having
both.

Personally I think there needs to be greater interaction between
QtQuick developers and QtQuick users. One of Qt's great strengths
before was that the developers were also the target audience, we wrote
the very APIs that we'd want to use (and it worked so well that all
our seasoned experts have left to become full-time Qt users ;) ). But
Qt is C++ and primarily crewed by C++ developers, so this
declarative/scripting thing targets a different audience than
ourselves. I think that means we need to work harder to remain close
to our users and ensure that our APIs truly provide value. So I would
recommend all persons developing QML/QtQuick to join the users ML too,
and that API discussions involve the users list sometimes.

--
Alan Alpert