…and i use the word awesome precisely, for making my first application was an awe-inspiring experience. i could make a better screenshot, i could work it untill i really do have plasma pong, but ffs it took two hours for a standing start! never having done any c++ let alone work with a fluid library before, let alone… yeah, i could go on. possibly the better route is just to try and sample some of my communication in the 24 hours since then…
› was going to come down to that, let me know how it is
btw the workshop was great, or rather the workshop was a decent enough workshop (memo is a great teacher, btw) but OF is really really great. i think i probably got a lot more out of the workshop that some others, as i’ve spent so much time coding this last year or two i was able to dive straight into c++ and OF, but really OF comes highly recommended: quick to code, fast to execute, and vast in its scope. if you can do processing, OF is pretty much processing for grown-ups.
› so how you finding OF? you know you can just recompile it for the iphone…
simply that i could write that from a standing start in a weekend OF workshop blows my mind.
› dude, are you saying what I’m thinking you are saying? Create a layer for openframeworks -> QCplugin!?!? so you can compile an openframeworks app as a QCPlugin!? cos that would be ace! lets do it!!
i am saying something like that =]
you either create a OFRenderer class that is patterned on QCRenderer, or yeah, you somehow get an OF app to impersonate a QCRenderer or QCComposition.
either of which would blow the doors off. OF wrapped and frame-driven from cocoa (ie. NSOpenGL, CV display link), coding rendering pipelines that go through both OF and QC, OF as plug-ins for all QC enabled apps… la la la le la shazaam.
note - a zip of the project is attached, frozen at the minute it first was alive as a working plasma pong. so its not to be taken as an example of coding best practice, but just to illustrate what two hours can get you. space bar to start, a/z and k/m for the paddles.