Method for Adapting a Processing Library to the Web
Abstract
A method for the adaptation of libraries done by users for the Processing graphics language, based on Java, to the graphics engine for the web processing.js, based on WebGL and JavaScript is presented. Various methods to make adaptations to the web are reviewed. In our approach, we propose to create a architecture that is compiled to JavaScript, using Google Web Toolkit technology, in order to maintain the user library without modifications and making the adaptation in a single trunk of development. The architecture has three-tiers: the user library, a layer that simulates the Processing behavior and a layer to use the user library in the web. It is presented two prototypes of adapted libraries.
Downloads
References
C. Reas and B. Fry, Getting Started with Processing. O’Reilly, 2010.
L. Burdy, A. Requet, and J.-L. Lanet, “Java applet correctness: A developer-oriented approach,” in FME 2003: Formal Methods. Springer, 2003, pp. 422–439.
Adobe, “Adobe flash platform,” http://www.adobe.com/flashplatform/, 2012. [Online]. Available: protectunhboxvoidb@xpenalty@Mhttp://www.adobe.com/flashplatform/
Microsoft, “Microsoft silverlight perspective 3d graphics,” 2012. [Online]. Available: http://www.microsoft.com/silverlight/perspective-3d-graphics/
D. Brutzman and L. Daly, X3D: extensible 3D graphics for Web authors. Morgan Kaufmann, 2010.
J. Resig, B. Fry, and C. Reas, “Processing. js,” 2012.
T. Parisi, WebGL: Up and Running. O’Reilly Media, 2012. [Online]. Available: http://shop.oreilly.com/product/0636920024729.do
J. Vantomme, Processing 2: Creative Programming Cookbook: Over 90 Highly-effective Recipes to Unleash Your Creativity with Interactive Art, Graphics, Computer Vision, 3D, and More. Packt Publishing, 2012, chapter 9: Exploring JavaScript Mode.
P. team, “ Processingjs exhi bi ti on,” 2015. [Online]. Available: http://processingjs.org/exhibition/
K. Phillips, “ Toxiclibs.js open source computational design,” http://haptic-data.com/toxiclibsjs/, 2011. [Online]. Available: http://labs.hapticdata.com/2011/01/toxiclibs-js-open-source-computational-design/
Google, “Understanding the gwt compiler,” https://bit.ly/336nIFk, October 2012. [Online]. Available: https://bit.ly/3JcbPwV DevGuideJavaToJavaScriptCompiler
——, “Jre emulation reference,” https://developers.google.com/web-toolkit/doc/latest/RefJreEmulation, October 2012. [Online]. Available: https://developers.google.com/web-toolkit/doc/latest/RefJreEmulation
Oracle, “Stubs and skeletons,” 2010. [Online]. Available: http://docs.oracle.com/javase/7/docs/platform/rmi/spec/rmi-arch2.html
Google, “Coding basics - javascript native interface (jsni),” https://bit.ly/3uBDzHA, 2012. [Online]. Available: https://bit.ly/3uBDzHA
M. C. M. Ray Cr omwel l , “ gwt-exporter,” http://code.google.com/p/gwt-exporter/, 2012. [Online]. Available: http://code.google.com/p/gwt-exporter/
K. L. Damkjer, “Obsessive camera direction (ocd) reference,” http://www.gdsstudios.com/processing/libraries/ocd/reference/, 2009. [Online]. Available: http://www.gdsstudios.com/processing/libraries/ocd/reference/
M. Niemi, “Traer’s physics library to processing.js - notes,” http://svbreakaway.info/tp.php, 2011. [Online]. Available: http://svbreakaway.info/tp.php#tpjs
X, “processing adapted libraries,” http://goo.gl/KzvxH1, 2013. [Online]. Available: http://goo.gl/KzvxH1
J. T. Bernstein, “Traer.physics 3.0,” http://murderandcreate.com/physics/, 2010. [Online]. Available: http://murderandcreate.com/physics/
J. P. Charalambos, “Proscene description,” http://code.google.com/p/proscene/, 2011. [Online]. Available: http://code.google.com/p/proscene/
This article is published by LAJC under a Creative Commons Attribution-Non-Commercial-Share-Alike 4.0 International License. This means that non-exclusive copyright is transferred to the National Polytechnic School. The Author (s) give their consent to the Editorial Committee to publish the article in the issue that best suits the interests of this Journal. Find out more in our Copyright Notice.
Disclaimer
LAJC in no event shall be liable for any direct, indirect, incidental, punitive, or consequential copyright infringement claims related to articles that have been submitted for evaluation, or published in any issue of this journal. Find out more in our Disclaimer Notice.
