-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension documentation in Markdown #697
Comments
Oops. Actually,
|
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!
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 Anyway, I have just tried a conversion with
Oops. It existed before. I have to dig in old archives to restore it.
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 |
Hello @jpellegrini, Just a bunch of commits to add some documentation for GUIs in STklos (and show that I'm still alive). It is far from finished, and partially re-read. I have not converted yet the old documentation on fuse. |
Hello @egallesio ! |
I feel sorry for you and hope these issues will be solved soon. |
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)?
The text was updated successfully, but these errors were encountered: