You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the GAMA documentation generation process only works for the main gama project, generating documentation from @doc annotations of projects in the gama folder. Plugins not referenced in the gama.product are documented as "extensions", but they still need to be in the gama project folder, even if plugins from gama.experimental are imported in the same Eclipse workspace as gama.
Documentation of @doc annotations of experimental plugins are available as tooltips from Gama, but I would like to also take advantage of those annotations to generate wikis about the usage of each plugin. This might help to solve issue #27.
Even if wikis are not generated for experimental plugins with the MainGenerateWiki.java tool, docGAMA.xml files are still generated for them (not sure exactly what build process is responsible for this). In consequence, it is possible to run the msi.gama.documentation on the gama.experimental plugins with little hacks.
Here is a proof of concept with the chemmisol plugin I am currently developing:
The msi.gama.documentation project is not yet adapted to experimental plugins, since the source and destination directories are hardcoded. I however think the tool could be easily improved to make it more generic and adaptable.
Adapting the gama.wiki base files in the gama.experimental.wiki files (e.g. Home.md, _Sidebar.md, ...) should then be enough to generate a gama.experimental wiki containing the @doc based documentation of all experimental plugins.
Since a wiki would be very helpful for the usage of my plugin, I think I could try to make this feature available if the Gama team thinks it is relevant.
The text was updated successfully, but these errors were encountered:
I think it could be a good idea yes, especially since we have plugins like genstar that used to be in the kernel (and thus to had their automatic documentation on the website) that moved to experimental.
What are your thoughts @AlexisDrogoul ?
Currently, the GAMA documentation generation process only works for the main
gama
project, generating documentation from@doc
annotations of projects in thegama
folder. Plugins not referenced in thegama.product
are documented as "extensions", but they still need to be in thegama
project folder, even if plugins fromgama.experimental
are imported in the same Eclipse workspace asgama
.Documentation of
@doc
annotations of experimental plugins are available as tooltips from Gama, but I would like to also take advantage of those annotations to generate wikis about the usage of each plugin. This might help to solve issue #27.Even if wikis are not generated for experimental plugins with the
MainGenerateWiki.java
tool,docGAMA.xml
files are still generated for them (not sure exactly what build process is responsible for this). In consequence, it is possible to run themsi.gama.documentation
on thegama.experimental
plugins with little hacks.Here is a proof of concept with the chemmisol plugin I am currently developing:
The
msi.gama.documentation
project is not yet adapted to experimental plugins, since the source and destination directories are hardcoded. I however think the tool could be easily improved to make it more generic and adaptable.Adapting the
gama.wiki
base files in thegama.experimental.wiki
files (e.g. Home.md, _Sidebar.md, ...) should then be enough to generate agama.experimental
wiki containing the@doc
based documentation of all experimental plugins.Since a wiki would be very helpful for the usage of my plugin, I think I could try to make this feature available if the Gama team thinks it is relevant.
The text was updated successfully, but these errors were encountered: