0.9/todo.txt
Back to the directory
1.0:
- homepage link in main window?
- www: screenshot on main page?
- don't check right after browser startup? (-> talk with Cinu)
- Check this page:
* very often (each ..h/m)
* often (each ..h/m)
* rarely (each ..h/m)
Warning: Monitoring sites increase transfer.
Don't check too often!
(in main window and prefs)
(+ ablity to configure intervals)
(defaults: 20m, 1h, 24h)
(changelog: can set different check interval for every site)
- use HTTP 1.1 - don't download when possible
- http:// prefix problem (what if user forgots to add it?)
- notifications when multiple items change?
***
2.0 or later:
- TODOs from the code
- http auth
- select&test a sound file from prefs
* how to notify?
- less offensive, change icon in bookmarks? (http://mozillapl.org/forum/post-126609.html#126609)
- run external app?
- in status bar?
- few sites at a time - collect all?
- accesskeys
- notify by sms?
- Mozilla Suite/SeaMonkey compability (? http://kb.mozillazine.org/Reusing_tabs_for_the_same_URL)
- http://kb.mozillazine.org/Javascript_coding_guidelines - of there are no other items ;-)
http://www.w3.org/Protocols/rfc2616/rfc2616.html
http://ii.yebood.com/viewtopic.php?t=1183
http://ii.yebood.com/viewtopic.php?t=1321
http://www.ii.uni.wroc.pl/~marcinm/dyd/obiekty/projekty.html
On update:
- make tests (any regressions?)
- www: pl+en changelog
- www: pl+en docs
- www: pl+en update screenshots
- www: pl+en version number (download info on every site - header)
- www: check how many times the previous version was downloaded
- build new .xpi
- upload new .xpi
- upload all www files + source to server
- test site & download file
- update and upload update.rdf
- test the update
- put a tag in svn
- update at addons.mozilla.org
- marketing - blog (ak74.wordpress.com), forums, etc.