Forum Replies Created
I assume you’re referring to the OS X Version of Procoding (on iOS it’s of not possible, because node.js cannot be installed on iOS).
Yes, on the Mac it’s possible: You just need to have node.js installed. Then with any sketch (except for processingjs sketches) choose “Run with node.js” from the File menu. Alternatively, press Cmd+B or use the “run with” toolbar button.
I’ve just seen the Facecandy readme and it says that you can connect via WebSockets. This topic might help you to get started: http://www.audiocommander.de/blog/forums/topic/udp-socket/
Not sure if this helps?
you can delete sketches with a long-press. It should bring up a menu that has a delete option. If you’re using iCloud you can select if you want to remove the local version only or also delete the sketch from iCloud.
Procoding Mobile 3.5.1 has just been approved and released after just 4 days review time (version 3.5 was over 16 days in review!).
With this update, hopefully all major bugs should be squished related to iOS 8.
Update: Procoding 3.5 is still in review,
Once this gets approved, I have another update 3.5.1 ready for submission that will fix most of the current bugs on iPads running iOS 8 (mainly the non-working second order menu sheets).
Thanks for your patience, and sorry again that the transition to iOS 8 had been a bumpy road this year. There were really many hidden bugs introduced with iOS 8…
Please have a look at the provided demos, (automatically installed on iOS, right below the File > Open menu on OS X). Some of them contain additional resources, some of them don’t.
I’m not sure if you’re talking about the OS X or the iOS version,
Procoding Mobile also contains a help section that explains the features of the templates and has many links to useful sites and online tutorials that should help you to get started.
Weather or not to use the Canvas or non-Canvas template… I can’t say, depends on what you want to do ;-)
The fix is now available as an update through the Mac App Store.
Let me know if it works for you.
More Yosemite related updates will be released whenever they are ready…
Update: Procoding 3.4.1 hotfix has just been released, though it doesn’t yet fix the bug completely (it just has additional infos about the bug).
And Procoding 3.5 which contains a bugfix for this issue (and some iCloud syncing fixes for users that upgraded to iCloud Drive) has just been submitted. I expect this update to be reviewed (and hopefully approved) within the next one or two weeks. It’ll also come with an exciting new feature!
Sorry for the wait, but this one has been really hard to track down.
I’ve submitted an update, which does not solve the problem, but should prevent the processing.js related crashes in 50% of all cases and give at least some feedback.
I am working on a proper fix, but that will take some time. Unfortunately the crash happens deep inside the WebKit framework – and because I really don’t want to fix the AJAX file loading mechanism of processing.js (which is the main cause for this issue), there are just a few possibilities left, all of them not really trivial.
However, as I do not expect that the bug in UIWebView will be fixed by Apple (UIWebView is deprecated with iOS8, so I can’t imagine they will be investing any time in fixing things) and WKWebView is still not really usable, I need to change some internals in order to make it work again. I already have an idea which might result in a nice additional feature…
Remember, so far only iOS 8 and processing.js is affected. Everything should work fine on iOS 7 and with all other JS libs.
Will keep you updated…
I have submitted an update to the app store.
I hope it’ll pass the review soon.
Another update with more fixes for Yosemite (mainly the mis-colored tab bar) is in the works…
Thanks again for contacting me,
There’s a severe issue with processing.js crashing the webview on a refresh. Only iOS 8 with processing.js is affected. All other JS libraries work fine.
So, unfortunately I had to reject the current version and have to investigate this issue further.
Sorry for the delay, but as I see, many users are expecting processing.js to work, so I have to see if I find a workaround for this nasty issue. Will keep you updated…
okay, here’s some background info:
– there’s only processing.js affected, that’s the reason I didn’t notice it yet
– Yosemite changed the way WebViews are caching. In all other libraries that load scripts, I am appending the current date/time, to prevent caching. Processing.js however loads local files with an xhr (AJAX request), which might be cool and nerdy stuff, but it’s the main reason things are so broken, e.g. no local previews for processing.js in Chrome and Firefox.
The good news is: I found a workaround.
The bad news is: it might violate the AppStore guidelines, so I don’t know if it’ll get accepted.
I’m working on a fix with high priority and will keep you updated!
Thanks again for reporting this.
thanks for the report, I will investigate this.
Will work on a bugfix!