Education/Projects/ProcessingForTheWeb: Difference between revisions

Added section on high-level tasks
(Added link for processing.js task list)
(Added section on high-level tasks)
Line 77: Line 77:


[http://opencode.media.mit.edu/tool/open_code/info OpenCode] (by Kyle Buza and Takashi Okamoto) is an alternative attempt to create a web equivalent of the Processing desktop environment. To quote from the website, "What Processing has done for simplified graphics programming, OpenCode hopes to do for simplified access and interaction with Web-accessible content." It can be thought of as a Java-based Processing environment "in the cloud"; Processing sketches are based to a server to be compiled into applets, and the resulting applets are run in the user's browser using the Java plugin. The environment includes special libraries to enable interaction with web services, and advanced users can write their own libraries in Java.
[http://opencode.media.mit.edu/tool/open_code/info OpenCode] (by Kyle Buza and Takashi Okamoto) is an alternative attempt to create a web equivalent of the Processing desktop environment. To quote from the website, "What Processing has done for simplified graphics programming, OpenCode hopes to do for simplified access and interaction with Web-accessible content." It can be thought of as a Java-based Processing environment "in the cloud"; Processing sketches are based to a server to be compiled into applets, and the resulting applets are run in the user's browser using the Java plugin. The environment includes special libraries to enable interaction with web services, and advanced users can write their own libraries in Java.
=== High-level tasks ===
The following are some possible high-level tasks for this project:
* Address outstanding bugs and feature deficiencies for processing.js vs. the original Java-based Processing implementation. For more information on what needs doing see the [[Education/Projects/ProcessingForTheWeb/Tasks|detailed task list]].
* Surface and address bugs or performance issues in the Mozilla JavaScript engine that prevent processing.js from offering comparable performance to the Java-based implementation of Processing.
* Look at Bespin architectural or other changes that would be needed in order to support a web-based development environment for Processing.
* Design and implement a first-cut prototype for a full web-based Processing environment.
* (Longer-term) Create a full Canvas 3D implementation and hook it into processing.js.
* (Longer-term) Look at possibilities for adding web-centric functionality to Processing (e.g., new functions to access web-based services from Processing sketches).
* (Longer-term) Look at possibilities for adding collaborative capabilities to a web-based Processing environment.


== Notes ==
== Notes ==
Confirmed users
610

edits