Skip to content
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

Create technical documentation #29

Closed
GoogleCodeExporter opened this issue May 10, 2015 · 8 comments
Closed

Create technical documentation #29

GoogleCodeExporter opened this issue May 10, 2015 · 8 comments

Comments

@GoogleCodeExporter
Copy link

There is an urgent need for technical documentation that gives users and site 
managers an easy manifest on how tom implement and configure the geoext-viewer. 
Enduser documentation is outside the scope of the geoext-viewer and should be 
managed by the parties that create derived work.

Original issue reported on code.google.com by milovand...@gmail.com on 4 Apr 2011 at 7:54

@GoogleCodeExporter
Copy link
Author

Openlayers uses NaturalDocs to generate technical documentation from 
comment-blocks within the code. I would advice to follow a similar pattern as 
it will be easiest to maintain the documentation from within the code.

Original comment by milovand...@gmail.com on 4 Apr 2011 at 7:55

@GoogleCodeExporter
Copy link
Author

Original comment by jus...@gmail.com on 20 Apr 2011 at 11:51

  • Added labels: Project-RVOB3

@GoogleCodeExporter
Copy link
Author

Original comment by jus...@gmail.com on 12 May 2011 at 2:19

  • Added labels: Milestone-Release0.5

@GoogleCodeExporter
Copy link
Author

Issue 34 has been merged into this issue.

Original comment by jus...@gmail.com on 23 May 2011 at 9:35

@GoogleCodeExporter
Copy link
Author

For release 05. We will create the general framework to generate the 
documentation, both the API docs from the code (ala OpenLayers and GeoExt using 
NaturalDocs or something similar) and the overall User/Developer doc setup 
possibly using Sphinx.
It is the intention to use the website www.heron-mc.org as the starting point. 
The Google code Wiki will not be extended, as we may move completely away at 
some later stage.

Original comment by jus...@gmail.com on 23 May 2011 at 9:39

  • Added labels: Priority-High
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

Also on advise from Bart and the use of Sphinx in GeoExt and GXP I will setup a 
Sphinx documentation for both regular docs as well as the API (via JST 
template).

Original comment by jus...@gmail.com on 24 May 2011 at 7:36

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

The doc overall framework is there. We still need to fill the API doc (thourhg 
JS comments) and some primer docs. I'll keep this open so the work is not 
forgotten.

Original comment by jus...@gmail.com on 31 May 2011 at 1:23

  • Added labels: Milestone-Release0.7
  • Removed labels: Milestone-Release0.5

@GoogleCodeExporter
Copy link
Author

Ok let's put this in 0.6 and make (a) new ticket(s) that makes remaining doc 
work explicit. Everything is there on http://heron-mc.org

Original comment by jus...@gmail.com on 31 May 2011 at 1:39

  • Changed state: Fixed
  • Added labels: Milestone-Release0.6
  • Removed labels: Milestone-Release0.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant