19,800
edits
(meh) |
No edit summary |
||
| Line 4: | Line 4: | ||
:Please experiment with that method elsewhere. Automatic or not, your method would in this particular case make the script look like a truckload of non-stop ASCII, which is, well, impractical and ugly. Breaking up the stuff in sections is a huge improvement with tutorial-style documentation in mind and will take zero time as compared to writing up the comments anyway. | :Please experiment with that method elsewhere. Automatic or not, your method would in this particular case make the script look like a truckload of non-stop ASCII, which is, well, impractical and ugly. Breaking up the stuff in sections is a huge improvement with tutorial-style documentation in mind and will take zero time as compared to writing up the comments anyway. | ||
::[[User:Geyser|geyser]] 19:32, 21 March 2008 (CET) | ::[[User:Geyser|geyser]] 19:32, 21 March 2008 (CET) | ||
:::Well, I wasn't going to say it, but I happen to think blurbs of ASCII interrupted by awkward redundant section headers in another font is uglier. I don't see solid ASCII as ugly in the first place. Also, we could use the style of commenting you use [[Quotes/Consoles/level_1e|here]], which would make comments stand out more against the monospaced font. | |||
:::Also, it wouldn't be more work to use my method, once it's implemented. You just enclose every function name with <nowiki>{{Anchor|functionname}}</nowiki> and then, in theory, put a template like {{AnchorTOC}} at the top and it will list the anchors. | |||
:::But, what is it exactly that you don't like about the way the ASCII text looks? The monospacing? I mean, weren't you doing exactly this when you linked [[IGMD/Airport#Original_contents|here]] to those text files? Weren't the "overcommented" versions just going to be the ASCII versions with comments in them? --[[User:Iritscen|Iritscen]] 20:19, 21 March 2008 (CET) | |||