Changeset 700
- Timestamp:
- 09/12/10 22:18:43 (21 months ago)
- Location:
- trunk/reference
- Files:
-
- 2 modified
-
idldoc-reference.rst (modified) (2 diffs)
-
idldoc-tutorial.rst (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/reference/idldoc-reference.rst
r699 r700 85 85 ------------- 86 86 87 TODO: what is a format style? legacy format styles "IDLdoc", "IDL"; not recommended for new comments88 89 87 90 88 rst format style … … 589 587 #. code blocks 590 588 #. headers 591 #. image directive 592 #. embed directive 593 #. title directive 589 590 *Directives* provide a more general markup syntax. Currently, there are three directives defined: 591 592 #. image directive 593 #. embed directive 594 #. title directive 595 596 The "image" directive allows images to be placed into comments. To use, put the following on the end of a line:: 597 598 .. image:: filename 599 600 where `filename` is any image file format read by `READ_IMAGE`. The `filename` specified will be copied into the output directory. 601 602 The "embed" directive allows `.svg` files to be embedded in the documentation. To use, put the following on the end of a line:: 603 604 .. embed:: filename 605 606 The "title" directive is available to provide a title for `.idldoc` files:: 607 608 .. title:: cpt-city color tables 609 610 This title is used for the `.idldoc` file in the table of contents of available documentation. 611 594 612 595 613 verbatim markup style -
trunk/reference/idldoc-tutorial.rst
r699 r700 25 25 The rst format and markup styles are inspired by reStructuredText and Markdown projects 26 26 27 I DLdoc 3.0 was completely rewritten separately from the IDLdoc 2.x code base.27 In *The Mythical Man Month*, Fred Brooks argues to "build one to throw away." For reasons out of my control, IDLdoc 3.0 was completely rewritten separately from the IDLdoc 2.x code base and now follows Brooks' rule. 28 28 29 29 This tutorial intends to get a new user up to speed in using IDLdoc in the simplest way using the newer, more modern style of IDLdoc commenting. Don't worry, though, IDLdoc still supports legacy commenting styles so you don't have to go changing existing documentation (unless you want to make use of some of the cool, new features!). Experienced users will probably learn some new things too, since documentation for IDLdoc has been spotty in the past. … … 70 70 71 71 TODO: "rst" is the modern supported style for both format and markup in current versions of IDLdoc (although not the default); legacy format/markup is described in the reference manual. 72 73 The format style defines the format for comments within specially marked comment headers. Comment blocks which start with `;+` and end with `;-` are considered by IDLdoc:: 74 75 ;+ 76 ; This is a comment block. 77 ;- 78 79 These comments start with a general description of the file or routine they are documenting, but the format styles define a format for adding comments about particular aspects such as individual parameters/keywords of a routine or author of a file. 80 81 There are three format styles allowed in IDLdoc comments: "rst", "IDLdoc", and "IDL." The "IDLdoc" and "IDL" format styles are for provided for legacy documentation headers; new comments should be written in the "rst" format style. 72 82 73 83
