Proposed Changes to VTK: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(Suggestion for changing the way we use Doxygen to document our API.) |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
The following are proposed, broad changes to VTK as suggested by users and developers. These changes are posted here for approval by the VTK ARB (Architecture Review Board). Please review and provide feedback on the VTK Developers mailing list. | The following are proposed, broad changes to VTK as suggested by users and developers. These changes are posted here for approval by the VTK ARB (Architecture Review Board). Please review and provide feedback on the VTK Developers mailing list. | ||
* [[VTK/VTK integration point support| VTK integration point support]] | * [[VTK/VTK integration point support| VTK integration point support]] | ||
Latest revision as of 19:45, 25 February 2013
The following are proposed, broad changes to VTK as suggested by users and developers. These changes are posted here for approval by the VTK ARB (Architecture Review Board). Please review and provide feedback on the VTK Developers mailing list.
- Email the VTK developer's mailing list when a new bug report is added.
- Run VTK/Utilities/Doxygen/doc_header2doxygen.pl on the headers, commit the result and use Doxygen directly in the future - allowing the developers to group etc according to documentation guidelines. This would also allow new developers to read Doxygen tutorials and use standard Doxygen comments in headers - lowering the barrier to entry.
