[Interest] making qt examples more verbal

[Tero.Aijala at nokia.com]

Hi,

On 14.11.2011 8.23, "ext alex.blasche at nokia.com" <alex.blasche at nokia.com>
wrote:

>
>
>>-----Original Message-----
>>From: interest-bounces+alex.blasche=nokia.com at qt-project.org
>>[mailto:interest-bounces+alex.blasche=nokia.com at qt-project.org] On Behalf
>>Of ext markc at renta.net
>>Sent: Monday, 14 November 2011 15:48
>>To: interest at qt-project.org
>>Subject: Re: [Interest] making qt examples more verbal
>>
>>On 14 Nov 2011, 05:29:37, alex.blasche at nokia.com wrote:
>>>> So, I've decided to clone and work with 4.8, as this is probably
>>>> going to be the latest released and includes all the latest version
>>>> of examples and demos.
>>>
>>> If you want to work on the location enabled weatherinfo then you have
>>> to use qtmobility.git/master. There is no point in using a 4.7/4.8
>>> branch as the weatherinfo example in Qt can never be location enabled.
>>
>>Do you mean exactly git://gitorious.org/qt-mobility/qt-mobility.git?
>
>Yes, thank you for making it explicit.
>
>>Would it be best to future proof this effort and work from a Qt5 base?
>
>It really depends on your preference. I agree with the implication in
>your question. I'd prefer spending effort on Qt5 but I don't want to push
>anybody into a corner.
>
>Qt5 has a big advantage as it directly ties into the current efforts and
>Gerrit is in place. Qt4.x and Mobility would only have the standard
>Gitorious merge request system which is inferior.

Right, Qt5 where the open governance processes work currently, and that is
where the future development obviously is happening. The ex-mobility APIs
are there as well, and they are experiencing major changes.

The Qt Mobility side is in the old Gitorius merge system, and is quite
stable, only receiving bug fixes basically.

So where you contribute depends on your preferences: if you want to
improve the examples for people on the existing, deployed
Qt4.x/QtMobility1.2 device & codebase, then work on the Qt Mobility
master. If you want to be future proof and on the bleeding edge, help with
the Qt5 effort.

Best case would be if you can do both, as that could generate some
valuable insights and feedback for the Qt5 work :)

Br,

Tero


>
>--
>Alex
>_______________________________________________
>Interest mailing list
>Interest at qt-project.org
>http://lists.qt-project.org/mailman/listinfo/interest