Fruitbat todo

- can we still end up with the stores window coming up too soon?
- fuzzy ranking and cutoff of tag suggestions
- fulltext-based suggestions
- choose *fastest* store in multiplex for read, not *master*
- when accessing slave store, display as read-only and have menu item to emancipate store
-> consequence: master store on s3, slave stores locally for caching and offline access
- per-session global undo/redo - so we can undo the "oh shit I did not mean to do that" moments
- we do really want a comment field, methinks
- change "delete original" to "store a copy", reverse polarity
- make loading store configs from prefs much more robust: individual store config load faults should be insulated, and less verification at config load time - so what if it references a nonexistent folder
- overlay triggers too fast
- screenshot doesn't work - switch overlay to opaque square
- really want "create new document and add page" shortcut
- data commit progress would be awesome
- hitting esc in the add page dialog opens the completion menu
- suggestions are *dreadful* - create new system synthesising probabilities from colour, full text?
- negative number sorting support
- in main list, sort by name of tag, and put colonned tags first
- icon should be opaque gray, sorry.
- narrow the colour bands?
- when opening multipage document, always end up on page 2!
- move suggested/all tags to the right for more consistent layout
- try to steal plausible date out of document?
- centre new docs instead of insetting them
- somehow talks about 100s of docs on startup
- manage stores windows comes up too quickly
- can then open stores twice
- if you enter all store details and leave the naming to last, the OK button is not enabled
- does not handle being unable to find store very well
- should confirm before removing store!
- store manage and edit still fugly
- need Window menu
- remove test menu for 1.0
- better open dialog somehow
- consistent visual language
- HTML manual with quickstart
- simple website
- what are the semantics of savetocache?
- fix that some things which really should take datachange just take change
- want tests of what happens to data integrity if storage substrate suddenly bye-byes
- the interfaces really want javadoc
- PUT DOWN VERY PRECISELY WHAT DATA/METADATA IS EXPECTED TO BE IMPLICITLY THERE IN STORES AND DOCS
- classes should have at least a 1-sentence desc
- explain what the hell a prefix b-tree is, and why there are string pools
- write down what the threading model is
- explain about how the UI is blocked
- make it clear which code is to be run from threads. if twere possible to separate out the threaded bits from documentframe into their own class that would be awesome