Anonymous user
User talk:Morn: Difference between revisions
no edit summary
(Responses) |
No edit summary |
||
Line 18:
:::::::I'm wondering if there should be a better way for source code comments. I don't mean putting // or REM or # in the source code, but a template solution that e.g. displays a red dot in front of a line and when you hover over it with the mouse pointer, it shows the comment. Right now explanations are relegated to Talk pages and that seems like an inconvenient solution. --[[User:Morn|Morn]] 15:10, 26 December 2010 (UTC)
::::::::Explanations currently ''should'' be placed in proximity to the code, either as language comments or next to the block of code. Some contributors, for various reasons (I assume concerns about oververbosity are one of them), put their explanations in the Talk pages. Sometimes, questions are raised about whether/how an example solves a task, and the matter is worked out in the talk page. (In some of those instances, additional documentation of the code example may well be warranted.) --[[User:Short Circuit|Michael Mol]] 15:47, 26 December 2010 (UTC)
:::::::::This is also a good Wiki: http://en.literateprograms.org/Tic_Tac_Toe_%28Python%29 I'll have to check if that's already listed under related sites here. Perhaps they have a little too much documentation (it's almost like a tutorial).
:::::::::How about a short reader survey, e.g. using [[mw:Extension:QPoll]]? If you know what readers want to see more or less of, which features they find helpful, etc., that might help you determine what to tackle next. Essentially, there are other similar sites, so it's a question of how to differentiate Rosetta Code from the rest. --[[User:Morn|Morn]] 16:19, 26 December 2010 (UTC)
| |||