Processing and text

I’m getting back into making processing stuff (as you can see from the sketch below), so next I’m hoping to do something a little more ambitious, using text for something more interactive.

Anyway, it’ll take me a little while to get my head around text in processing,

More Processing

[processing width=”640″ height=”480″ file=”http://www.ashleyelsdon.com/wp-content/uploads/2012/01/Mouse_Makes_some_shapes_1.jar” method=”inline”]Load the applet[/processing]

This is a simple sketch I was fiddling with last night. I know it doesn’t do much, but it does show a tiny bit of what you can do with processing in just a few lines of code. Of course, what I’d really like to do with processing is more audio related and I’m hoping to explore more of this soon. Thought I’d share though.

Is it worth me building my own local App Inventor?

Yesterday or late last night at any rate Google announced that they were releasing the code for their Android App Inventor product. You can download it here. Now I’m considering whether I should attempt to compile and run it locally myself.

It sounds like a kind of cool project to try out, but almost certainly one that will cause lots of problems for me. I’ll let you know if I can make it work, or even if I try.

Running iziBasic and ViziBasic under StyleTap

So today is my last day of using the StyleTap trial. I knew that I’d have to get the last bit of testing done today to see if I could use iziBasic and ViziBasic on the emulator. The short answer? You can. In fact, in some ways they work better, especially in terms of being able to zoom the screen, which is very handy when you’re not using a stylus.

So I ran a ‘generate code and compile’, from Vizibasic, and that worked fine, and a compile from iziBasic and that worked too. All systems go then. Looks like I’ll be buying StyleTap after all!

Codify becomes Codea

This is an interesting app and has started up my interest in on-board apps for programming again. Of course iOS apps that are programming apps can’t write actual apps themselves just run their code inside the app. Even so, they are fun to play with and Codea which was called Codify seems particularly interesting.

So I’m going to give it a go again, and see if I can make anything good with it. If I do, I’ll publish the results.

Messing around with Processing

I’ve been messing around with Processing JS for a few days as it seems to be easier to put .js sketches into a web site than standard Processing sketches, and it is. But, whilst it makes a lot of sense to use processing.js with WordPress, sadly processing.js isn’t so good at audio, and a lot of my processing stuff is audio related.

So I’m going back to straight Processing for now as I know I can get the audio librarys to work with that.

Never mind

Messing about with App Inventor

I’ve been playing with Google’s Android App Inventor site, and it is a lot of fun to mess about with. However, at the moment, it is unlikely to be useful for any kind of serious musical application building.

There is talk of being able to introduce extensions to App Inventor so you could do more with it. Things like using Pure data would be useful if you could integrate that into what App Inventor is about, and maybe that will come at some point, but at the moment musical applications will be somewhat limited and toy-like.

Still. Good fun to play with.


Loading…

Something went wrong. Please refresh the page and/or try again.