gtk-rs
Generate urls (when possible)
@GuillaumeGomez, if diffs line this is really what you want, then all good. But IMHO link in markdown looks like [I'm an inline-style link](https://www.google.com)
<!-- struct AboutDialog -->
-The `AboutDialog` offers a simple way to display information about
+The `./struct.AboutDialog.html` offers a simple way to display information about
a program like its logo, name, copyright, website and license. It is
also possible to give credits to the authors, documenters, translators
Current version also not right. Ticks go inside brackets.
The [AboutDialog](./struct.AboutDialog.html) offers a simple way to ...
or
The AboutDialog offers a simple way to ...
I'm getting redundant Exts like this with gtk:
-Use `BoxExt::set_child_packing` to reset the expand,
+Use `BoxExtExt::set_child_packing` to reset the expand,
- `Box:spacing` property. If `child` is a widget at one of the
+ [`Box:spacing`](./struct.Box.html) property. If `child` is a widget at one of the
I'm not sure it's a good idea to link property and signal references to just the struct's page. There'd be expectation that they lead somewhere useful.
Generally, are you sure it'd not be better to expand analysis::symbols instead? There seem to be duplication of concerns in the making (I assume you'll want to process methods too).
This is a first shot. I have a very bad understanding of all the underlying mechanisms, which lead to the code you can see now.
The symbols module only tracks names now but it could also store types. It could be difficult to make it play nice with the struct/trait dichotomy. But in return you'd get the rest function handling for free.
I fixed the "ExtExt" issue. I guess running the analysis twice created it. You'll certainly find out better than I.
IMHO this link need hashtag (when signals added)
[`AboutDialog::activate-link`](struct.AboutDialog.html)
Also don't see reason to having link to struct.AboutDialog.html in same file.
Possible link to wrong page
[`gio::Application::startup`](struct.Application.html) signal
Only found other possible hashtagable is properties (very few, ex. Label) and Widget::draw that can be signal or function.
Other wrong link: must link to TreeViewColumnSizing (if we have separate page for enum)
[`TreeViewColumnSizing::Fixed`](struct.Fixed.html)
I've taken another look at analysis::symbols, it should be possible to make it track additional type information. There already is a provision for dealing with trait methods.
@EPashkin I think we've come to a point when it's necessary to make a separate analysis pass, so the codegen could just look up analysis results.
After #267 classes and interfaces will get analyzed by the time codegen is run ensuring the trait methods get fixed up. So moving forward with this would be to make analysis::symbols aware of item types and teach it to emit relative paths for links.