Comments on: iProcessing Puts Processing.js on iPhone – But What About Browsers?

By: Gopi Palaniappan

Gopi Palaniappan — Sun, 07 Nov 2010 20:47:23 +0000

I just posted an Android app that renders processing scripts over Webview. Check this out: http://code.google.com/p/my-processing/

By: Enlaces sobre el iPad

Enlaces sobre el iPad — Fri, 16 Apr 2010 08:41:30 +0000

[...] Create Digital Motion » iProcessing Puts Processing.js on iPhone – But What About Browsers? No es para el iPad, pero la opción de usar Processing es atractiva. [...]

By: Make iPhone apps using Processing? : SAI

Make iPhone apps using Processing? : SAI — Mon, 05 Apr 2010 04:58:58 +0000

[...] better coverage on Create Digital Motion & CreativeApps. Category: [...]

By: Peter Kirn

Peter Kirn — Wed, 17 Feb 2010 08:30:15 +0000

SkyRon: I wouldn't nail any coffins, but it means that between JavaScript and old-fashioned Java, you can target just about anyone using Processing. (You'll need Java for old browsers that don't support HTML5.)

I can also say that for *me*, Processing long ago eliminated any desire to use Flash. That's just me, though.

By: SkyRon™

SkyRon™ — Wed, 17 Feb 2010 02:08:08 +0000

While this news is not quite at the "Max for Live" level of CDM excitement, it is pretty exciting!

So, if iProcessing/Processing.js can prototype, do cool animations on multitouch devices, and cross the iPhone/Android divide (and if we can work out those little HTML5 issues), does this put a nail in the Flash coffin, so to speak? (at least until CS5 comes out . . .)

By: Olivia Spensor

Olivia Spensor — Sat, 13 Feb 2010 07:41:51 +0000

Well It's good I tried it on safari on iphone what I like about this is It’s a good proof of concept and prototype of how you might generally wrap those features on multiple platforms.

By: Joe Zydeco

Joe Zydeco — Fri, 12 Feb 2010 19:35:06 +0000

Luckybite used iProcessing to prototype the app, not build the final app.

By: zach

zach — Fri, 12 Feb 2010 13:46:33 +0000

I think one of the nice things about getting x project on platform y, even if it's not the most direct way to work with it, is the kind of things you learn along the way. For example, getting OF on the iphone involved abstracting the windowing toolkit, which allows OF to run as a full fledged cocoa app or headless, etc. The same thing of getting processing.js on iphone — there's quite alot of interesting bridge work being done there. At the moment, I'm researching OF on adroid NDK at the moment, not because it's an ideal fit (by any means) but because sometimes fitting a square peg through a circular hole leads to curious discoveries, and the more options and devices that your sketches and code can run on, the better. I haven't looked at the N900, but we've got a few at the school I teach in, might be interesting to see how that works.

Anyway, I'm psyched about projects like this and ingenuity involved. Had the same feeling as when I saw seriality:

http://zambetti.com/projects/seriality/

with a little bit of glue, hooking anything to anything is possible

By: Peter Kirn

Peter Kirn — Thu, 11 Feb 2010 19:02:49 +0000

1. I'm hopeful, at least. SOME things have been accepted.

2. Yes, you'd need the SDK in order to deploy your apps.

By: Bill Van Loo

Bill Van Loo — Thu, 11 Feb 2010 19:00:49 +0000

A couple thoughts:

1. The iProcessing developers (Luckybite) used the iProcessing framework to develop their BirdBox app, which is available on the App Store. Given that, wouldn't it make sense to assume that merely using this framework wouldn't prevent an app from being accepted?

2. My assumption is that you'd still need the $99 iPhone Developer SDK to be able to build apps for your own device, just like any other native iPhone apps. Correct?

The mere fact that this is available is really exciting. It certainly opens up new avenues for artists, designers, and coders who use Processing, as well as new ways to build apps for the iPhone family of devices.

Bill