1: <h1>Annozilla 'to do' list</h1>
2: <h2>Short term</h2>
4: <li><strike>Move 'Server prefs' and 'Edit Site List' back into the main panel on Firefox</strike> (fixed in CVS)
5: <li>Don't write to window.status?
6: <li>Rename "Post"/"Update" to "Save"
7: <li>Make all sidebar options available via menu (not just context menu)
8: <li><strike>Fix memory leaks (3 objects leaked per window)</strike> fixed in CVS
9: <li>Are we slowing down new window/tab creation by loading so much code into the context menu? (use nsISubscriptLoader or whatever it's called?)
10: <li><strike>Get <code>"Stylesheet annotations.css not found: using chrome://annozilla/content/annotations.css"</code> in error console.</strike> Update: this is intended behaviour, however I have removed the logging to the console.
11: <li><strike>Autoloading for tabbed browsing?</strike> Implemented by CGH.
12: <li>From an empty sidebar (showing "No annotations loaded"), create an annotation without first loading the annotations for the page. The new annotation is added for the list but "No annotations loaded" is still present.
13: <li><strike>Remove extra nodes from DOM when a highlight is deleted. (At the moment we just remove the highlighting.)</strike>
14: <li>Open annotation window by double-clicking on icon opens window at unreasonably small size. <strike>Or sometimes get "Sorry, couldn't download the annotation body."</strike> - fixed by allowing multiple annotation windows
15: <li>Integrate Firefox 2 built-in spelling checker.
18: <h2>Medium term</h2>
20: <li>In the Server Options panel, display "Local Server" not "urn:localserver" (if possible)
21: <li>Use XBL language binding everywhere
22: <li>Rework classes using model/view/controller terminology
23: <li>On sidebar load with no servers, make it easier to load the Server options panel
24: <li>Move multiple server support into an 'Advanced' panel???
27: <h2>Long term</h2>
29: <li>XBL for annotation icons and/or highlights
30: <li>The 'fastback' feature would presumably leave annotation icons/highlights in the document but not held by Annozilla. Could the annotation data be held in the document, with DOM UserData? (speculation, I don't know whether this is possible.)
31: <li>Test cases
32: <li>Unit tests