I've checked all of qtnetwork and everything already had the \inmodule.
Rich.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
I can build docs to create qt.qch for now (today, master).
2012/8/25
> You might be right in theory, but we are currently simply not able to
> build the docs in a modular way.
--
Best Regards
Yuchen
___
Development mailing list
Development@qt-proj
On Aug 24, 2012, at 11:21 AM, ext Oswald Buddenhagen
wrote:
> On Fri, Aug 24, 2012 at 11:13:49AM +0200, Vandonderen Casper (Nokia-MP/Oslo)
> wrote:
>> What I want to do in QDoc is to automatically set the module to the value
>> of the "project" variable in the qdocconf file (if no \inmodule co
On Fri, Aug 24, 2012 at 11:13:49AM +0200, Vandonderen Casper (Nokia-MP/Oslo)
wrote:
> What I want to do in QDoc is to automatically set the module to the value
> of the "project" variable in the qdocconf file (if no \inmodule command is
> specified).
>
that sounds about right.
> This means that c
>>
>>On Thu, Aug 23, 2012 at 07:30:23AM +, ext
>>casper.vandonde...@nokia.com wrote:
>>> example:
>>> /*!
>>>\class QObject
>>>\inmodule QtCore
>>> ...
>>> */
>>>
>> isn't it a *tad* weird that sources in a modularized package need to
>> declare in which package they are, several hundr
On Aug 23, 2012, at 1:58 PM, ext Oswald Buddenhagen
wrote:
> On Thu, Aug 23, 2012 at 07:30:23AM +, ext casper.vandonde...@nokia.com
> wrote:
>> example:
>> /*!
>>\class QObject
>>\inmodule QtCore
>> ...
>> */
>>
> isn't it a *tad* weird that sources in a modularized package need t
On Thu, Aug 23, 2012 at 07:30:23AM +, ext casper.vandonde...@nokia.com
wrote:
> example:
> /*!
> \class QObject
> \inmodule QtCore
> ...
> */
>
isn't it a *tad* weird that sources in a modularized package need to
declare in which package they are, several hundred times? i call that
"s
On quinta-feira, 23 de agosto de 2012 12.10.35, Thiago Macieira wrote:
> On quinta-feira, 23 de agosto de 2012 07.30.23, casper.vandonde...@nokia.com
> wrote:
> > What needs to be done:
> > - Find the qdoc comment containing \class in your classes.
> > - Add a new line containing the text "\inmodul
On quinta-feira, 23 de agosto de 2012 07.30.23, casper.vandonde...@nokia.com
wrote:
> What needs to be done:
> - Find the qdoc comment containing \class in your classes.
> - Add a new line containing the text "\inmodule [modulename]"
> - Do this for each of the classes, that does not have an \inmod
Hi,
To be able to properly generate modularized Qt documentation we need QDoc to
know in which module a class resides and I need help with this if we want to
get modularization (mostly) done before the Qt 5 release.
Previously QDoc would guess to which module a class belonged by finding
keywor
10 matches
Mail list logo
