Changeset 687 for trunk

Show
Ignore:
Timestamp:
09/03/10 16:49:55 (21 months ago)
Author:
mgalloy
Message:

More tutorial stuff.

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • trunk/reference/idldoc-tutorial.rst

    r684 r687  
    55:Revision: $Revision$ 
    66:Date: $Date$ 
     7 
    78 
    89Introduction 
     
    1314Features?  
    1415 
    15   #. API documentation for both developers of the code base and users of the code base 
    16   #. analyze code like complexity 
     16  #. API documentation for both developers and users of the code base 
     17  #. analyze code for things like code complexity 
    1718 
    1819Similar things?  
     
    135136File formats? 
    136137 
     138embed directive:: 
     139 
     140    .. embed:: filename 
     141     
     142File formats? 
     143 
    137144title of an `.idldoc` file, title directive:: 
    138145 
     
    141148Appears in navigation links on the left/title of the page 
    142149 
    143 headers 
     150headers, =, -, or ~ anywhere, but most useful in `.idldoc` files 
     151 
    144152 
    145153IDLdoc options 
     
    148156user vs. developer documentation, `USER` keyword, private/hidden tags (and attributes) 
    149157 
    150 overview='overview', footer='footer' 
     158The `FOOTER` keyword can specify a file to include at the bottom of each page of output. 
    151159 
    152 /embed and /nonavbar (standalone vs. web server) 
     160When producing HTML documentation, there are often two cases that need to be handled:  
     161 
     162  #. documentation served on a web site and intended to be served as a full collection 
     163  #. documentation pages intended to be handed out individually, e.g., giving someone a `.pro` file and its generated HTML documentation file 
     164   
     165In the later case, it is often useful to set the `EMBED` and `NONAVBAR` keywords. The `EMBED` keyword embeds the, rather large, CSS file into each HTML page. This is inefficient for a full documentation set on a web site because in that situation, each page can just refer to a common `.css` file. The `NONAVBAR` keyword simply omits the navigation bar at the top of the page which is not needed when only one HTML page is given but useful to navigate a full documentation set. 
    153166 
    154167index_level=1