Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- art:processing [2016/11/26 12:50] – spitz
+++ art:processing [2018/04/24 12:08] (aktuell) – Externe Bearbeitung 127.0.0.1
@@ Zeile 1: / Zeile 1: @@
-[[http://processingjs.org/articles/p5QuickStart.html]]
+====== try ======
-Processing.js Quick Start - Processing Developer Edition
+[[http://ibulla.com/process/]]
-Introduction
-This quick start guide is written from the standpoint of a Processing developer. No HTML or JavaScript knowledge is assumed, and only basic Processing knowledge is necessary.
+====== processing ======
-  *     For the Impatient
+[[https://processing.org/reference/]]
-  *     Why Processing.js?
-  *         The Web: from Java to JavaScript
-  *         Processing.js uses Modern Web Standards
-  *     Writing a Processing.js Sketch
-  *     Obtaining Processing.js
-  *     Creating a Processing.js Web Page
-  *     Running your Processing.js Web Page
-  *     Things to Know as a Processing Developer using Processing.js
-  *         Processing.js has no data directory
-  *         Processing.js implements Processing, but not all of Java
-  *         Processing.js only has two rendering modes
-  *         Division which is expected to produce an integer might need explicit casting
-  *         JavaScript, and as such Processing.js, has no "char" datatype
-  *         Processing.js has to cheat to simulate Processing's synchronous I/O
-  *         Processing.js requires more care with variable naming than Processing
-  *         Processing.js needs your help when overriding overloaded superclass methods
-  *         Calling color() with out-of-range values produces unpredictable colors
-  *     It is possible to put Processing code directly in your web page
-  *     Whatever you can do with the web, you can do with Processing.js
-For the Impatient\\
+====== processing.js ======
-If you're in a rush, here's what you need to know:
-Processing.js is written in JavaScript, and uses HTML5's <canvas> element. It converts your Processing code to JavaScript and runs it. To use it, download Processing.js here: downloads Make your Processing *.pde files as you normally would, for example hello-web.pde Create a web page that includes Processing.js as well as a <canvas> with info about where to get your sketch file (you can specify multiple *.pde files, separating them with spaces):
+[[http://processingjs.org/articles/p5QuickStart.html]]
 <code>
 <script src="processing-1.0.0.min.js"></script>
 <canvas data-processing-sources="hello-web.pde"></canvas>
 </code>
-Load your web page, and it will parse, translate, and run your sketch in the browser.\\
-Why Processing.js?\\
-The Web: from Java to JavaScript
-Processing is built using Java. It was created at much the same time that the web was starting. At this time the choice of the Java language, and Java Runtime, as implementation targets for Processing made a lot of sense. In the mid-1990s, Java was poised to become the language of the web, with Applets and other Java technologies being used broadly on the client-side. Even Netscape, who created the language which would eventually become the lingua franca of the web with JavaScript, named their language so as to align themselves with the growing hype around Java.
-In the end, Java became an important server side technology, receding from the client-side and browser. Today, most web browsers still support Java Applets, by means of a binary plugin. However, few web developers deploy Java-based web applications now, due to long load and startup times and difficulties relying on Java (or compatible Java versions) being installed. This trend is not isolated to Java, but is happening to all browser plugins (e.g., Flash), which are becoming less popular as issues of security, installation, deployment, etc. make them inconvenient or risky.
-Another reason that plugins like Java and Flash have fallen out of favour is that recent advances in standard web technologies, specifically HTML5 and JavaScript, have made it possible to do things that previously depended on native (i.e., faster, compiled) code. Companies like Google, with GMail and Google Docs, or Scribd (see Scribd-in-HTML5) have shown that HTML, CSS, and JavaScript alone are enough to build fast, full featured web applications.
-Processing.js uses Modern Web Standards
-Processing.js is built using JavaScript and HTML5. Processing.js is really two things: a Processing-to-JavaScript translator; and an implementation of the Processing API (e.g., functions like line(), stroke(), etc.) written in JavaScript instead of Java. It might seem odd at first to imagine your Processing sketches running in a browser, usually without modification. But this is exactly what Processing.js enables.
-Processing.js automatically converts your Processing code to JavaScript. This means that you don't have to learn JavaScript in order to run your code in a browser. You can, quite literally, write your code using the Processing IDE like you always have, and follow the steps below to get it running on the web. There's nothing new to learn, beyond getting a simple web page created.
-Under the hood, Processing.js uses the new HTML5 canvas element to create your sketch's graphics. The canvas element is a new feature of the web, and is either implemented or will be implemented by all major web browsers. All Processing drawing features have been reimplemented in Processing.js to use canvas, so any browser that supports canvas will also support Processing.js.
-Here's a sample of a Processing.js sketch running in the browser. If you can see it working, your browser supports everything you need already, and you can move on to instructions below.
-Writing a Processing.js Sketch
-There's nothing you should do differently to write sketches for Processing.js: you write your Processing.js code exactly like Processing. For most people, this will mean using the Processing IDE, which has the nice benefit of letting you write, run, and test your code all in once place. Remember, any valid Processing sketch should also be a valid Processing.js sketch.
 If you want to experiment with web-based Processing.js code editors, you can also try these: