so i've started to make a ChucK library for Processing:

=>PhucK

its main feature is to enable and simplify the export of standalone apps which have full ChucK power built in. Should work on Windows and Mac.

Since this is a very early first release it is highly likely to not just work as expected.
I'd be happy to receive any feedback, especially bug reports!

Check out the example sketch included with the library, it explains how to use it.
I'm going to implement more functionality in future releases.

(also posted here)

i wanted it to look less complicated, but yeah the style will probably change around for a bit..

so here is an example app for Windows and Mac.

If you have a spare minute, i would appreciate if you could try and run this on your machine and tell me if it worked or not. You should get sound & animation.

thanks for trying Cedric!

okay this is weird as i'm testing it on the same version of Windows. I reckon you too have the latest Java installed?

I've changed the Java JRE system library to J2SE-1.5 in Eclipse, and re-exported the example app. Maybe that was the culprit? Links above updated.

agh, this is just sad.  
i don't know how to narrow down the issue. If you still have a little time and patience, you could download the library, and see if you can run the examples from the PDE?

It seems to work on most Mac systems, no clue what it could be.

Here's what the library does, just to document:

the ChucK binary for Windows and Mac is located inside the library like this:



it's not in the standard data folder because i couldn't figure out how to get it out of there.

on runtime, if phuck.launch() is called, the ChucK binary for the respective OS is extracted from the jar and executed from a TEMP location, together with any ChucK script files stored in the app (or in the chuck folder of the sketch, if it's run from the PDE). On Windows it will also set a WINXPSP2 compatibility flag in the registry before execution, because ChucK's OSC implementation seems to be broken on Win7 x64.

If it's running, in your task manager you should see a process named chuck[+some numbers]. When the process is ended, it will be deleted from the TEMP location (this seems to work rather well in OS X, sometimes it doesn't in Windows for a reason. If you check your default TEMP folder there might be an accumulation of ChucK binaries, which is bad. Working on it! In Windows the registry flag is then also removed).

If you quit the app in any way, the chuck process is set up to notice this (it keeps pinging Processing via OSC) and will finally crash itself.