Currently the API documentation only covers the parts of design which are finished, for the rest
of the features it is hard to find a proposal, design spec. or just a decision written in emails. For
a better orientation of module developers make the documentation complete in the sence that
it would cover all features and areas planned for 4.0. Some of them can be unfinished but need
at least to be mentioned.
few notes for myself (what should be added):
1. overview (what can be customized by modules):
2. what will be changed/incomatible:
3. wizards and temlpates
4. how to implement resources and outputs (api, hints, examples)
5. how to implement nested projects (hints, examples)
7. private settings
8. term: project nature
>3. wizards and temlpates
started, draft document can be found in CVS in projects module, \api\doc\dev_guide.html in
an example of a simple howto:
*** Issue 20213 has been marked as a duplicate of this issue. ***
needs to be completed for M3
Must-have features for milestone3, have impact on APIs (at least potential).
the docs are completed. they must of course be updated whenever we make changes/additions to APIs.