Extension documentation in Markdown

[jpellegrini]

The documentation for extensions is still in markdown format, and is not compiled into PDF or HTML...
A user on reddit was looking for the documentation for gtklos, and thought it didn't exist. Maybe we should convert it to adoc and auto-generate it? Also explain in the README where the documentation can be found (or even better, in the reference manual)?

[jpellegrini]

Oops. Actually,

• Doc for gtklos exists in markdown, but is not generated
• Doc for fuse does not exist (!)
• Doc for curl exists, in adoc format, and is being generated, but it stays hidden in a subdirectory of that extension

[egallesio]

I'm surprised there is still some interest for building interfaces in Scheme. I thought that this interest was lost a long time ago, now that everything is HTML based. Great!

* Doc for gtklos exists in markdown, but is not generated

That's true. But it is in a bad shape (there is only the introduction). My idea was to auto-generate most of the documentation by using stklos-pp (by introspection of the classes, it is possible to have the list of the field of each class and, with a short preamble, it should suffice).

Anyway, I have just tried a conversion with pandoc what we already have and it is really better.
It should be generated.

* Doc for fuse does not exist (!)

Oops. It existed before. I have to dig in old archives to restore it.

* Doc for curl exists, in adoc format, and is being generated, but it stays hidden in a subdirectory of that extension

It is normal that it is hidden, because extensions are not built by default (they use external libraries which can be absent on a given system). In fact, a make install could eventually install it, with the rest of STklos documentation.