-
Notifications
You must be signed in to change notification settings - Fork 1
TODO
qqueue edited this page Apr 16, 2013
·
3 revisions
Since c4 is still alpha, I don't really want to clutter the issue tracker.
User facing:
- generally working WYSIWYG posting
- generally working auto-updating
- generally working inline backlinks (manual threading)
- should retain state through page reloads
- Integrated gallery with board pages with auto-updating ("Browser"-like)
- Generally not ugly
Internal:
- Consistent naming and code style
- Dogfooding CustomEvent API as much as possible
- Automated tests for the parser
- IDB-based domain data cache (posts, threads, unreads)
- Updater state is no longer stupid
-
Code structure able to take outside libraries, like d3(Done) - Page loads still fast enough on my netbook
- Decent test coverage
- Customization GUI
- Support for other than firefox
- Fancy graphs
- machine learning stuff
- Rewrite posting
- feb 2012-era code, really gross. I want to do
contenteditableWYSIWYG anyway. - Need to really nail all the requests responses from
sys.4chan.org; write that spec, I guess
- feb 2012-era code, really gross. I want to do
- Rewrite updating
- There are still weird bugs. Might need to wait for testing framework on this
- Rewrite force-quotes
- it's a really great feature unfortunately implemented in a really slow fashion (DOM manip).
- Rewrite inlinereplies
- Need this a lot more robust and less coupled.
-
Rewrite backlinking implementation(Done) -
Factor out parsing concern(Done), maybe to another library entirely (likely happening) - Reorganize stylesheets
- The separate files are better but still not there
- Normalize coding style, names, etc
- With 4chan-JS, except where completely braindead (
tim)
- With 4chan-JS, except where completely braindead (
-
Explicitly wire dependencies with(Done)require() - Use outside components (maybe even literally) whenever possible.
-
timingfunctions can probably be replaced or extracted. - wider use of baconjs to replace imperative-looking code.
- The less code I have to look at the better, as long I don't sacrifice performance.
-
- Write feature and code specs/tests
- buster.js, but maybe mocha instead. Can't decide yet, need to run trials.
- data, spec for posting might become separate projects, along with the parser
- Deal with all the other
TODOandFIXMEtags in the source
- Ditch greasemonkey and become a real extension
- Make cross-browser extension wrapper
- Make heavier centralized 4chan statistics server, like an archiver but just data