TO DO

TO-DO

You can check out a Google calendar with some milestones and special dates on the dev process here

Short term (~One week)

• Complete wiki pages (including also formatting them for better readability)
• Make a public Google calendar with my project schedule
• Continue making test classes for the existing gui-builder project, and document them
• Speak with Bernhard
• Find a better way for debugging
• Read and understand exactly what perfect recall implicates, and how is a perfect recall done
• Debug and finish ExtensiveFormTest.as
• Find the best way for making the GTE occupy the full-screen, and give it a better style than the current button.
• Find a good way to show errors, alerts and debug traces' 'log'. Implement it, and migrate all trace(), Alert.show() and throw new Error() from the code, to use Log class as a proxy
• Make a checkpoint system for Action History (making undo() usable in real-world executions :D)
• [Issue 3#] - Better zoom
• [Issue 5#] - Editable and selectable nodes
• [Issue 7#] - Display Equilibrium path

Long term (>One week)

• Design a schedule of the improvements for the gui ordered by which I believe should be better to implement first
• Follow the previous schedule! :P. First, for the improvements that are more related to usability, it will probably be useful to prototype them in Processing or Flash studio directly, to avoid the long compilation and testing times.
• After finishing this, continue with the planning inside the GSOC application (or any other task that may arise)