Proposed Changes to VTK: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(Added a new proposed change for VTK.) |
(Suggestion for changing the way we use Doxygen to document our API.) |
||
| Line 10: | Line 10: | ||
* Email the VTK developer's mailing list when a new bug report is added. | * 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. | |||
{{VTK/Template/Footer}} | {{VTK/Template/Footer}} | ||
Revision as of 19:02, 12 December 2009
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.
- Adding UserVoice to VTK similar to ParaView.
- 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.
