Education/Projects/ProcessingForTheWeb/Tasks

Summary

This page lists tasks to be done as part of the Processing For The Web project, in order to fully implement all of Processing in processing.js. The work is being led by David Humphrey and Al MacDonald, and done by students at Seneca College. You are welcome to join this work.

Task List

Bugs

The following list of Bugs, Features, and Functions was compiled by Al MacDonald.

Bug	Description
// Comment	Using double slashed comments // at the end of any script will cause REGEX to loop on parsing, subsequently crashing browser. Quick solution is to add a blank line at the end of every script.
mouseX & mouseY	mouseX and mouseY are returned as incorrect values when the canvas is a child of a relative element.
nf()	Using nf() on some numbers crashes FireFox. EG: String sf = nf(9.012, 3, 5); from http://processing.org/reference/color_datatype.html will not work.
keyCode, CODED, etc	Keyboard functions need fleshing out and cross-browser/cross-platform testing.
The Angel Bug	When the regex parse encounters strings with a comma in, it parses the word before the comma as a variable. Work around is to escape strings... String myString = “this \, is a string”; But that is in no way ideal. More info: http://hyper-metrix.com/processing-js/docs/?page=Angels%20Weep
Drop frame system	A method to drop frames that are not drawn in time. This would be great for media-syncing if you want your app to stay in-time with audio and video. Not sure how plain-old JS timers will handle this... but it's worth testing

Missing Features

This is a list of all the out-standing functions in the Processing.js implementation. A more detailed description of the unfinished functions can be found at: http://processingjs.org/reference. (Click “toggle all” to see the list.)