Closed agalbachicar closed 2 years ago
Some comments
1 - For maliput_py
we are building docs but dsim_docs_bundler
isn't collecting them.
At the moment there is no sensitive documentation because the package only contains bindings. Probably creating a doc file in maliput_py
, (maliput_bindings.h) just to document bindings and let doxygen parse it could be the way to go.
2 -
maliput_malidrive xodr tools.
we probably could add a doc at maliput_malidrive/src/applications commenting about the applications so as let doxygen to parse it.3 - We should also document plugin architecture focused on the RoadNetwrok plugin.
Define whether to include delphyne repos into doxygen documentation. If yes, do it!
It was agreed to add it.
maliput_documentation
: See documentation.rstmaliput_documentation
dependency. https://github.com/ToyotaResearchInstitute/maliput_infrastructure/pull/231maliput_integration applications
maliput_documentation
page https://github.com/ToyotaResearchInstitute/maliput_documentation/pull/65@francocipollone I think we are only missing the maliput_visualizer documentation, right? Isn't it partially covered by the Delphyne Guide 2 as delphyne demos are?
@francocipollone I think we are only missing the maliput_visualizer documentation, right? Isn't it partially covered by the Delphyne Guide 2 as delphyne demos are?
maliput_viewer
isn't documented in the Delphyne guide.
Would you want me to add a section with that information?
Let's do it to wrap up this effort.
Let's do it to wrap up this effort.
Done.
Part of #135
Should document into maliput_documentation (logging here because it affects repositories out of the scope of maliput repos now):