On Wednesday 13 August 2014 11:58:33 David Edmundson wrote:
> All fixed!
>
> Some important notes:
>
> QtDoc changes will be in 5.4. I can just upload my generated .tags
> file to the api.k.o server in the meantime.
>
> It requires explicitly stating inheritance in documentation
> i.e
>
> /**
>
All fixed!
Some important notes:
QtDoc changes will be in 5.4. I can just upload my generated .tags
file to the api.k.o server in the meantime.
It requires explicitly stating inheritance in documentation
i.e
/**
@class Text
@short A text label styled using the plasma theme fonts and colou
Some progress:
https://bugreports.qt-project.org/browse/QTBUG-40551
My bug report got moved to confirmed + P2-Important.
I'm not sure what that actually means, but it certainly sounds encouraging :)
David
___
Plasma-devel mailing list
Plasma-devel@kde.o
I'll file a bug report in Qt. We won't get an immediate fix, but it
might get something for future.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
On Mon, Jul 28, 2014, at 15:26, Aleix Pol wrote:
> On Mon, Jul 28, 2014 at 8:07 PM, Marco Martin wrote:
>
> > On Monday 28 July 2014, Aleix Pol wrote:
> >
> > > > does somebody knows if is possible with the markup used now for
> > > > extracting documentation to still have comments to document al
There are .tags file made for most of Qt but not for qtquickcontrols.
In order to make it work automatically we'd have to fix QtDoc first.
:(
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Doxygen from QML seems to come from http://agateau.com/projects/doxyqml/
The way external linking with doxygen works is you have a .tag file
which contains the ID of the upstream component and a link to that
webpage. I don't know whether the normal .tag file contains QML
stuff...
_
On Mon, Jul 28, 2014 at 8:07 PM, Marco Martin wrote:
> On Monday 28 July 2014, Aleix Pol wrote:
>
> > > does somebody knows if is possible with the markup used now for
> > > extracting documentation to still have comments to document all the
> > > properties, even those *not* defined in the qml f
On Monday 28 July 2014, Aleix Pol wrote:
> > does somebody knows if is possible with the markup used now for
> > extracting documentation to still have comments to document all the
> > properties, even those *not* defined in the qml file in question?
>
> It should probably look more or less like
On Mon, Jul 28, 2014 at 6:11 PM, Marco Martin wrote:
> Hi all,
>
> right now the plasma qml components are documented not bad, like:
>
> http://api.kde.org/frameworks-api/frameworks5-apidocs/plasma-framework/html/classorg_1_1kde_1_1plasma_1_1components_1_1TextField.html
>
> however, porting them
10 matches
Mail list logo
