I'm going to make some changes once the 3 remaining open issues in the design forum have been addressed. Firstly, all further such issues will go into the project tracker under "feature requests". Only much more open-ended stuff will go into the design forum.
Secondly, after the issues presently in the design forum have been resolved (but before any other changes) there will be a cleanup session forming 4 parts:
1. Insert placeholder steps for ones that are just @todo at the moment. Consider executing other @todos.
2. Terminology: making sure words are being used consistently, adding new terms when they're obviously needed, and adding a glossary with their definitions. The glossary will go in CVS since it will be prone to changing.
3. Attempt to break down the 40-odd steps into some structure. There will be a preference for contiguous runs of steps (so there is a well-defined intermediate between blocks) and I might aven go to 2 levels of structure with one for runs that are really only broken down for testability and then another level for the major conceptual areas.
4. Fill in more detailed descriptions of the steps including code fragments (but don't have to be from the same prorgam).
The idea is not to lock down the design (it will never really be locked down) but to "raise the game" in terms of coherance, checkability and readability. Future re-ordering of steps will be more onerous, but is still completely OK and better than haxoring the steps to get around bad ordering.
All this should help to uncover silly errors in the steps too.
Might as well add these four things to the tracker too!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm going to make some changes once the 3 remaining open issues in the design forum have been addressed. Firstly, all further such issues will go into the project tracker under "feature requests". Only much more open-ended stuff will go into the design forum.
Secondly, after the issues presently in the design forum have been resolved (but before any other changes) there will be a cleanup session forming 4 parts:
1. Insert placeholder steps for ones that are just @todo at the moment. Consider executing other @todos.
2. Terminology: making sure words are being used consistently, adding new terms when they're obviously needed, and adding a glossary with their definitions. The glossary will go in CVS since it will be prone to changing.
3. Attempt to break down the 40-odd steps into some structure. There will be a preference for contiguous runs of steps (so there is a well-defined intermediate between blocks) and I might aven go to 2 levels of structure with one for runs that are really only broken down for testability and then another level for the major conceptual areas.
4. Fill in more detailed descriptions of the steps including code fragments (but don't have to be from the same prorgam).
The idea is not to lock down the design (it will never really be locked down) but to "raise the game" in terms of coherance, checkability and readability. Future re-ordering of steps will be more onerous, but is still completely OK and better than haxoring the steps to get around bad ordering.
All this should help to uncover silly errors in the steps too.
Might as well add these four things to the tracker too!