On Thu, May 16, 2013 at 3:15 AM, Pasion Jerome wrote:
> Hello,
>
> For C++ API changes, it's easy to tag with the \since command ("\since 5.1",
> for example).
> For QML types, we don't have a clear way of aggregating new changes because
> the types are tied to the
> QML modules ("\inqmlmodule Q
On 16 May 2013 13:11, Shawn Rutledge wrote:
> Alternatively we could change all the \since to use Qt versions, since the
> module versions are such a mixed bag. Qt versions constitute a timeline, at
> least.
>
This wouldn't work for modules that are developed and released
separately from the cor
On 16 May 2013, at 2:11 PM, Shawn Rutledge wrote:
> Alternatively we could change all the \since to use Qt versions, since the
> module versions are such a mixed bag. Qt versions constitute a timeline, at
> least.
But then again the point is to also document what version of a module you need
dditions manually. For
> 5.2, I assume that the QML module versions will be incremented, so we need
> to look at the issue more seriously.
>
> Cheers,
> Jerome P.
>
> Fra: Alan Alpert [4163654...@gmail.com]
> Sendt: 16. mai 2013 01:26
>
sion Jerome
Cc: development@qt-project.org
Emne: Re: [Development] Documentation Review for 5.1
On Wed, May 15, 2013 at 5:05 AM, Pasion Jerome wrote:
> Hello all,
>
> I would like to ask the module maintainers (and the community in general) to
> go over the documentation before the 5.1 final pa
On Wed, May 15, 2013 at 5:05 AM, Pasion Jerome wrote:
> Hello all,
>
> I would like to ask the module maintainers (and the community in general) to
> go over the documentation before the 5.1 final packages are out.
> Specifically, the module maintainers can check that their C++ and QML APIs
> are
Hello all,
I would like to ask the module maintainers (and the community in general) to go
over the documentation before the 5.1 final packages are out. Specifically, the
module maintainers can check that their C++ and QML APIs are visible and
accessible.
Some Qt 5.1 pages to review:
1) "What'
