rework options page
laforge49 opened this issue · comments
The options page in the wiki has gotten large. And we will be adding even more.
The use of options is the key to or composition mechanism. For now, we can break it down by function, but keep everything in a single map. If we go to separate maps, then we would want to go with Stuart's components or something that builds on it. But lets start with just a documentation change for now.
Looking at components-- https://github.com/stuartsierra/component
Circular dependencies are not allowed. The easy way to handle this is to think of the virtual aa structures and the database as comprising a single component, all be it the parts are fully decoupled.
This means that the transaction logger will be the second component.
OK, options have been grouped into read string, aa structure and database options.
Lets take this a bit further and show options by database. Motivation: heifer will not simply be adding options like yearling did.
Done, complete with a page index.