On Thursday, 10 August 2017 at 14:59:52 UTC, Adam D. Ruppe wrote:
On Thursday, 10 August 2017 at 14:55:06 UTC, Mike Wey wrote:
[...]
Oh, I see. My generator lists them on the index, but doesn't
recreate it each time, it just links. For example:
On Thursday, 10 August 2017 at 14:55:06 UTC, Mike Wey wrote:
The problem was that there are a few large classes at the start
of the hierarchy, and with the old version of ddox the function
pages would not only be generated for the base class, but also
for all the derived classes.
Oh, I see.
On 10-08-17 15:57, Adam D. Ruppe wrote:
On Saturday, 5 August 2017 at 14:02:09 UTC, Mike Wey wrote:
One issue is the shear size of the generated documentation, though the
current version of ddox no longer generates a ton of unused files
bringing the size down from 15-20GB to a mere 2GB.
On Saturday, 5 August 2017 at 14:02:09 UTC, Mike Wey wrote:
One issue is the shear size of the generated documentation,
though the current version of ddox no longer generates a ton of
unused files bringing the size down from 15-20GB to a mere 2GB.
what?! I'm not actually sure how much gtk
On 04-08-17 17:24, Gerald wrote:
On Friday, 4 August 2017 at 15:08:27 UTC, Mike Wey wrote:
Improving the documentation is something i want to do but there are
always some more important things to do. Like the Questions/Issues you
posted earlier.
So unless somebody volunteers it won't happen
On Friday, 4 August 2017 at 23:14:38 UTC, Adam D. Ruppe wrote:
On Friday, 4 August 2017 at 21:53:14 UTC, Johnson Jones wrote:
When I click on gtk on the link you gave it gives basically an
empty page(a single module).
Yeah, there is no overview page in the source code... but I can
make it
On Friday, 4 August 2017 at 21:54:26 UTC, Johnson Jones wrote:
On Friday, 4 August 2017 at 15:24:51 UTC, Gerald wrote:
On Friday, 4 August 2017 at 15:08:27 UTC, Mike Wey wrote:
[...]
Mike I had contributed the makeddox.sh script awhile ago, it
generates much nicer documentation then
On Friday, 4 August 2017 at 21:53:14 UTC, Johnson Jones wrote:
When I click on gtk on the link you gave it gives basically an
empty page(a single module).
Yeah, there is no overview page in the source code... but I can
make it create one automatically.
On Friday, 4 August 2017 at 15:24:51 UTC, Gerald wrote:
On Friday, 4 August 2017 at 15:08:27 UTC, Mike Wey wrote:
Improving the documentation is something i want to do but
there are always some more important things to do. Like the
Questions/Issues you posted earlier.
So unless somebody
On Friday, 4 August 2017 at 13:59:11 UTC, Adam D. Ruppe wrote:
On Friday, 4 August 2017 at 02:08:31 UTC, Johnson Jones wrote:
https://api.gtkd.org/gtkd/gtk/ApplicationWindow.html
So I ran gtkd through my doc generator too
On Friday, 4 August 2017 at 15:08:27 UTC, Mike Wey wrote:
Improving the documentation is something i want to do but there
are always some more important things to do. Like the
Questions/Issues you posted earlier.
So unless somebody volunteers it won't happen anytime soon.
Mike I had
On 04-08-17 03:51, Johnson Jones wrote:
https://api.gtkd.org
It is difficult to navigate.
1. clicking the documentation on the main site takes it to the
gtk.AboutDialog api. That is all it shows, I was confused at first, as
I'm sure most people would be.
2. The packages list lists all the
On Friday, 4 August 2017 at 02:08:31 UTC, Johnson Jones wrote:
https://api.gtkd.org/gtkd/gtk/ApplicationWindow.html
So I ran gtkd through my doc generator too
http://dpldocs.info/experimental-docs/gtk.ApplicationWindow.ApplicationWindow.html
and I didn't make a top-level package file
Also, interfaces are not linkable.
e.g., for gtk.ApplicationWindow, it inherits from gtk.Window but
I have to go back to the packages and scroll down to find
gtk.Window to see it's properties and methods. Would be nice if I
could just click on the gtk.Window and it jump me to it.
14 matches
Mail list logo