|View Issue Details [ Jump to Notes ] ||[ Issue History ] [ Print ] |
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000269||Documentation, Examples, and Web Site||Writing with Inform||public||2010-08-27 23:53||2010-10-29 09:23|
|Assigned To||emshort|| |
|Product Version||6E72|| |
|Target Version||Fixed in Version||6F95|| |
|Summary||0000269: Release documentation doesn't mention the useful public/private keywords.|
|Description||Currently for some release items the word "public" or "private" can be added to have the item included or excluded from the generated web page's list of links. This is a very useful feature, especially for the generated solution, which is private by default.|
This is not documented anywhere that I could find. If this was an internal only type thing then I suggest making it official just by documenting the current behaviour.
|Minimal Source Text To Reproduce|
[Don't forget to add a "*** solution" label to at least one skein node.]
Release along with a website and a public solution and private source text.
There is a room.
|Additional Information||The only way I even found out about this is by looking at the cBlorb code in order to modify it to get the solution link. After seeing that it supports both public and private requests I tried the obvious syntax and was pleasantly surprised.|
I also note that marking the "source text" as "private" not only doesn't link it but also skips the generation of the typeset HTML version; the only effect the statement has is to copy in source.txt. Personally I'd prefer it to still generate the HTML source; just not to link to it.
|Tags||No tags attached.|