1
edit
Changes
no edit summary
* I had to move the Processing.lib declaration back out of the constructor, it was being called from tests, without a new Processing object being created for test-harness-lib.js, line 4. This fixed the unit test problems.
* I am now pretty well versed in the flow of processing.js, they way it's called, what happens first, why, etc and learning more every day.
Monday May 17<br />
* Ontario Centers of Excellence booth.
Tuesday May 18<br />
* Ontario Centers of Excellence booth.
* [https://processing-js.lighthouseapp.com/projects/41284/tickets/232-test-removal-of-with-p removing with] was reviewed by David.
* Got to work on fixing those changes.
Wednesday May 19<br />
* Finished the previous fixes for [https://processing-js.lighthouseapp.com/projects/41284/tickets/232-test-removal-of-with-p removing with].
* Went through the test suit for my new patch, and found an error for key pressing, fixed it.
Thursday May 20th<br />
* Fixed another set of problems with [https://processing-js.lighthouseapp.com/projects/41284/tickets/232-test-removal-of-with-p removing with], mostly style and other nit picks.
* Ran through the new patch with the test suite, on opera, chrome, firefox, and minefield on linux.
* [https://processing-js.lighthouseapp.com/projects/41284/tickets/232-test-removal-of-with-p removing with] was checked-in that night.
Friday May 21st<br />
* [https://processing-js.lighthouseapp.com/projects/41284/tickets/232-test-removal-of-with-p removing with] is done, so I went on to my next big patch, which is [https://processing-js.lighthouseapp.com/projects/41284/tickets/664-remove-this-from-parsed-class-variables-and-go-with-thisgettersetter 664]
* In [https://processing-js.lighthouseapp.com/projects/41284/tickets/664-remove-this-from-parsed-class-variables-and-go-with-thisgettersetter 664] what I'm doing is taking what I learned from [https://processing-js.lighthouseapp.com/projects/41284/tickets/232-test-removal-of-with-p removing with] and improving what was done ages ago with the first with removal, which I hope can also solve my inheritance problems, which currently has three open tickets for inheritance [https://processing-js.lighthouseapp.com/projects/41284/tickets/554-override-not-working-as-expected 554] [https://processing-js.lighthouseapp.com/projects/41284/tickets/643-inheritance-problems-with-variables 643] and [https://processing-js.lighthouseapp.com/projects/41284/tickets/641-bug-in-the-handling-of-polymorphism-08-09 647] These all are very specific examples, but the problem is more general, and I hope by rewriting class parsing in this way, I can get inheritance just right, including super() and super. methods, which I'm going to solve by creating a super object within the scope of the sub class, and it'll be a copy of the base class, so by calling super.variableName, it will work without having to parse super., or without having to create a super function. Also static will need to be rewritten.
* I actually got very far on my class rewrite, and hope to have the first draft for peer review some time tomorrow after an evening of testing.
