n from the directory std/tools/haxedoc
into a folder that can be put online by your web server (using Apache with Neko is the topic of Chapter 9 ).
The documentation XML files should be located in the relative path ../data . The online version of
haxedoc doesn ??™ t accept any configuration parameter, the XML files must be named after their platform
( flash.xml , javascript.xml , neko.xml ), and must be present to prevent errors. What was said about
template.xml is still valid here.
Note that the links used in the documentation are in the format /api/package/type . This kind of path
must be mapped to the format used internally by the haxedoc.n application. This format is as follows:
haxedoc.n?class=package/type
170
Part I: The Core Language
To obtain the effect, add the following content to the file .htaccess in the same directory or create a
new one if it does not exist:
< FilesMatch ???^([_a-z0-9A-Z-])+$??? >
RewriteEngine On
RewriteRule /api/(.*) /haxedoc.n?class=$1
< /FilesMatch >
This will only work on the Apache web server with the mod_rewrite module activated.
Pages:
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338