Hey! I used to linger on here a few years back. Vaguely remember posting a few - hopefully helpful - posts... I disappeared off the face of the board after getting a full-time job staring at a computer screen: suddenly doing that in my spare time seemed less appealing. Not sure I ever properly said 'goodbye': guess life on the net is fairly transient...
Anyway, recent comments on a couple of things I posted on OpenProcessing prompted me to catch up with what's going on with Processing in general. Looks like there have been some big changes recently! No more applets is sad; but recent experience at work seems to justify the decision well enough. I had a good trawl on the Processing site and searched the forums but there doesn't appear to be much discussion on this; except a sensible enough explanation of the decision in the wiki (so hope raising this here is not inappropriate).
I'd be curious to know what direction people are taking now? I've been doing a fair amount of development work using Javascript recently - largely using skills I developed working with Processing :) - so it's tempting to look at Processing.js... But working with Javascript on a daily basis I'm well aware of the pros and cons (and maybe just want an escape!): and in general these all lead me to want to stick with 'pure' Processing; but it's cool to be able to present work online; so Processing.js has its appeal. But of course the various solutions to the 'limitations' of Javascript are of professional interest... And of course I don't yet fully understand just how different the syntax is; or how easy it is to define classes and do inheritance etc. in Processing.js.
So any suggestions on what I should do? Options seem to be to fix my sketches on OpenProcessing to work in Processing.js (if possible); or simply update them to work in Processing 2.0 and post the source elsewhere? If I've understood correctly I'm not able to update the applets on OpenProcessing using code refactored for Processing 2.0 which is what I was hoping to do...
And finally - nice to see some familiar names still on the forum :)
Anyway, recent comments on a couple of things I posted on OpenProcessing prompted me to catch up with what's going on with Processing in general. Looks like there have been some big changes recently! No more applets is sad; but recent experience at work seems to justify the decision well enough. I had a good trawl on the Processing site and searched the forums but there doesn't appear to be much discussion on this; except a sensible enough explanation of the decision in the wiki (so hope raising this here is not inappropriate).
I'd be curious to know what direction people are taking now? I've been doing a fair amount of development work using Javascript recently - largely using skills I developed working with Processing :) - so it's tempting to look at Processing.js... But working with Javascript on a daily basis I'm well aware of the pros and cons (and maybe just want an escape!): and in general these all lead me to want to stick with 'pure' Processing; but it's cool to be able to present work online; so Processing.js has its appeal. But of course the various solutions to the 'limitations' of Javascript are of professional interest... And of course I don't yet fully understand just how different the syntax is; or how easy it is to define classes and do inheritance etc. in Processing.js.
So any suggestions on what I should do? Options seem to be to fix my sketches on OpenProcessing to work in Processing.js (if possible); or simply update them to work in Processing 2.0 and post the source elsewhere? If I've understood correctly I'm not able to update the applets on OpenProcessing using code refactored for Processing 2.0 which is what I was hoping to do...
And finally - nice to see some familiar names still on the forum :)
1
