1
edit
Changes
no edit summary
* Finished [https://processing-js.lighthouseapp.com/projects/41284/tickets/764-pexpand-doesnt-need-a-temp-array 764], [https://processing-js.lighthouseapp.com/projects/41284/tickets/760-dont-assume-moz-attributes-exist 760], [https://processing-js.lighthouseapp.com/projects/41284/tickets/757-exit-does-not-remove-the-instance-from-the-processinginstances 757], [https://processing-js.lighthouseapp.com/projects/41284/tickets/752-arraylist-is-missing-setindex-value 752] and [https://processing-js.lighthouseapp.com/projects/41284/tickets/751-arraylist-is-missing-addint-index-object-value 751].
* started work on [https://processing-js.lighthouseapp.com/projects/41284/tickets/765-parraycopy-needs-to-be-fixed 765].
* finished [https://processing-js.lighthouseapp.com/projects/41284-processingjs/tickets/765-parraycopy-needs-to-be-fixed 765]
Wednesday July 14th<br />
* started work, and research on [https://processing-js.lighthouseapp.com/projects/41284/tickets/349-implement-createfont createFont]
Thursday July 15th<br />
* continued work on [https://processing-js.lighthouseapp.com/projects/41284/tickets/349-implement-createfont createFont]
Friday July 16th<br />
* Merged [https://processing-js.lighthouseapp.com/projects/41284/tickets/349-implement-createfont createFont ticket] into [https://processing-js.lighthouseapp.com/projects/41284/tickets/771-createfont-loadfont-and-pde 771]. This made sense for many reasons, the main one being that 771 covers problems in loadFont as well, when can then be wrapped by createFont.
* Continued research and development on createFont and loadFont, and I have it working cept a problem in chrome I have not been able to hammer out.
Monday July 19th<br />
* Today I fixed problems in tickets [https://processing-js.lighthouseapp.com/projects/41284/tickets/752-arraylist-is-missing-setindex-value 752], [https://processing-js.lighthouseapp.com/projects/41284/tickets/760-dont-assume-moz-attributes-exist 760], [https://processing-js.lighthouseapp.com/projects/41284/tickets/764-pexpand-doesnt-need-a-temp-array 764] and [https://processing-js.lighthouseapp.com/projects/41284/tickets/765-parraycopy-needs-to-be-fixed 765]
Tuesday July 20th<br />
* Started research on [https://processing-js.lighthouseapp.com/projects/41284/tickets/457-textmode textMode]
Wednesday July 21st<br />
* [https://processing-js.lighthouseapp.com/projects/41284/tickets/457-textmode textMode] might be over my head. I would love to take the challenge, but I don't think there is enough time for me to learn the 3D end, and still get it done. Might be better suited for Mike to take it, and I work on something else.
Thursday July 22nd<br />
* While assessing the current processing tickets for the next release, and more so for release 1.0, I noticed a handful of tickets are missing feature blockers
Friday July 23rd<br />
* I ended up drifting on textMode, into textAscent and textDescent, which are needed to finish textMode, which is currently under control of Mike. I will work with him to see what is best for both of us
Monday July 26th<br />
* no longer doing [https://processing-js.lighthouseapp.com/projects/41284/tickets/457-textmode textMode]. Gave it back to Mike because he is better suited to do it, and I am doing the following instead (we traded tickets)
* started work on [https://processing-js.lighthouseapp.com/projects/41284/tickets/454-textleading textLeading] because it is a missing feature blocked to processing.js
* started work on [https://processing-js.lighthouseapp.com/projects/41284/tickets/452-textascent textAscent]
* started work on [https://processing-js.lighthouseapp.com/projects/41284/tickets/453-textdescent textDescent]
Tuesday July 27th<br />
* Worked on my newly obtained tickets.
* I had previous research in them from researching textMode
Wed July 28th<br />
* while working on textLeading:
* I fixed an odd pixel that was slipping in between lines split on a string with newline characters. The extra pixel only existed using TOP, BOTTOM, and CENTER on the y axis. Basically, everything cept BASELINE, which was default... The problem was due to using the text size, instead of using text ascent, which is the same size for smaller fonts, but as the font gets larger, the gap is more noticeable.
* Noticed I totally overlooked the 4th and 5th parameters of text, which are height and width. This also needs to account for text leading using newlines OR spaces that push the text onto the next line. There is also a few pixel padding in the p5 version from the top of the box, to the first bit of text, which is dependent on the size of the font. I am not yet sure where they get this number, but I am looking through p5's source. The last final problem in textLeading() has to do with the number of pixels being padded between newlines and multiple lines.
Thursday July 29th<br />
* Finished off [https://processing-js.lighthouseapp.com/projects/41284/tickets/452-textascent textAscent], [https://processing-js.lighthouseapp.com/projects/41284/tickets/453-textdescent textDescent] and [https://processing-js.lighthouseapp.com/projects/41284/tickets/454-textleading textLeading].
* did [https://processing-js.lighthouseapp.com/projects/41284/tickets/754-in-class-default-scope-is-not-this-but-the-dom-window ticket 754]
[[category:Summer 2010 July]]
[[category:Scott's Work Log]]
