|
8 | 8 | <Heading>AutoDoc worksheets</Heading> |
9 | 9 |
|
10 | 10 | <ManSection> |
11 | | - <Func Arg="list_of_filenames : options" Name="AutoDocWorksheet" /> |
| 11 | + <Func Arg="[filenames,] [optrec]" Name="AutoDocWorksheet" /> |
12 | 12 | <Description> |
13 | 13 | The purpose of this function is to create stand-alone PDF and HTML files |
14 | 14 | using &AutoDoc; without associating them with a package. |
15 | 15 | <P/> |
16 | | - It uses the same optional record entries as <Ref Func="AutoDoc"/>, but |
17 | | - instead of a package name, you pass one filename or a list of filenames |
18 | | - containing &AutoDoc; text from which the document is created. |
| 16 | + Instead of a package directory, you pass one filename or a list of |
| 17 | + filenames containing &AutoDoc; text from which the document is created. |
| 18 | + Settings are supplied via an optional record using the same entries as |
| 19 | + the <A>optrec</A> argument of <Ref Func="AutoDoc"/>. Alternatively, you may |
| 20 | + omit <A>filenames</A> and specify the files via <C>optrec.autodoc.files</C>. |
19 | 21 | <P/> |
20 | 22 | A simple worksheet file can define title-page information and chapter |
21 | 23 | content directly in the source file, including example blocks. |
|
28 | 30 | <P/> |
29 | 31 | Since worksheets do not have a <F>PackageInfo.g</F>, title-page fields are |
30 | 32 | specified directly in the worksheet file. |
| 33 | + <P/> |
| 34 | + For backwards compatibility, worksheet calls still accept GAP global |
| 35 | + options for specifying the option-record entries such as |
| 36 | + <C>dir</C>, <C>scaffold</C>, <C>autodoc</C>, <C>gapdoc</C>, and |
| 37 | + <C>extract_examples</C>. |
| 38 | + However, this feature is deprecated. If its use is detected, &AutoDoc; |
| 39 | + prints a warning recommending the explicit options record instead. |
| 40 | + For example: |
| 41 | +<Log><![CDATA[ |
| 42 | + gap> AutoDocWorksheet( : autodoc := rec( files := ["worksheet.g"] ) ); |
| 43 | + #W AutoDocWorksheet: legacy ':' syntax is deprecated; use optrec instead |
| 44 | + ... |
| 45 | +]]></Log> |
| 46 | + |
31 | 47 | </Description> |
32 | 48 | </ManSection> |
33 | 49 |
|
|
83 | 99 | <Item> |
84 | 100 | The purpose of this parameter is twofold: to determine the package |
85 | 101 | directory in which &AutoDoc; will operate, and to find the metadata |
86 | | - concerning the package being documented. The parameter is either a |
87 | | - string, an <C>IsDirectory</C> object, or omitted. |
88 | | - If it is a string, &AutoDoc; interprets it as the name of a |
89 | | - package, uses the metadata of the first package known to &GAP; |
90 | | - with that name, and uses the <C>InstallationPath</C> specified in that |
91 | | - metadata as the package directory. If <A>packageOrDirectory</A> is |
92 | | - an <C>IsDirectory</C> object, this is used as package directory; |
93 | | - if the argument is omitted, then the current directory is used. |
94 | | - In the last two cases, the specified directory must contain a |
| 102 | + concerning the package being documented. The parameter is either an |
| 103 | + <C>IsDirectory</C> object or omitted. If |
| 104 | + <A>packageOrDirectory</A> is an <C>IsDirectory</C> object, this is used |
| 105 | + as package directory; if the argument is omitted, then the current |
| 106 | + directory is used. In both cases, the specified directory must contain a |
95 | 107 | <F>PackageInfo.g</F> file, and &AutoDoc; extracts all needed metadata |
96 | 108 | from that. The <C>IsDirectory</C> form is for example useful if you |
97 | 109 | have multiple versions of the package around and want to make sure the |
98 | 110 | documentation of the correct version is built. |
| 111 | + Passing a package name string is no longer supported. |
99 | 112 | <P/> |
100 | 113 | Note that when using <C>AutoDocWorksheet</C> (see |
101 | 114 | <Ref Sect='Section_AutoDocWorksheet'/>), there is |
|
256 | 269 | The value should be either <K>true</K>, <K>false</K> or a |
257 | 270 | record. If it is a record or <K>true</K> (the latter is |
258 | 271 | equivalent to specifying an empty record), then this feature is |
259 | | - enabled. It is also enabled if <A>opt.autodoc</A> is missing but the |
260 | | - package depends (directly) on the &AutoDoc; package. |
261 | | - In all other cases (in particular if <A>opt.autodoc</A> is |
| 272 | + enabled. In all other cases (in particular if <A>opt.autodoc</A> is |
262 | 273 | <K>false</K>), this feature is disabled. |
263 | 274 | <P/> |
264 | 275 | <P/> |
|
0 commit comments