• Hello,

    I am at the moment involved in interaction between Processing and Isadora, Isadora sending data via OSC to Processing, Processing sending image via syphon to Isadora. It works but it's not the easiest procedure, involving java coding in Processing, OSC and Syphon libraries etc.
    At the moment, there is a new processing model, using javascript inside browser, named P5 (http://p5js.org) and I am dreaming off a way to include P5 in Isadora, coding  directly with the same langage as Javascript actor and with the resulting image used directly inside Isadora.
    It would be very exciting, covering the features not well covered in Isadora, particles, colliders, procedural design etc. and resolving UTF-8 encoding!
    Unfortunately, it is absolutely out of my competences to work on it but perhaps there is someone in the team interested about a wedding between javascript actor and P5.js?
    waiting for 2.2 with great hopes and thank a lot for your work.

  • If only...! Problem is, P5js involves drawing directly from Javascript, which the Isadora actor cannot do. You’d still end up with a complex mess with LOTS of outputs that you’d have to link to Isadora actors which do the actual drawing of whatever it is.

    You’re back to using Isadora to do what it is designed to do. Isadora is a GUI so folks don’t have to code. If you’re having to start writing code to do what you want, you’re moving further away from what Isadora exists for.
    I’ve mentioned before that if Isadora’s JS Actor had some form of drawing canvas, or a virtual browser window to output to then you could bring in a wealth of javascript goodness - physics engines, animation & interaction engines, jQuery, p5 etc etc...  basically a fully fledged webkit actor with full js support. 

  • Hello,

    I don't completely agree with "If you're having to start etc.". Javascript actor is a proof that some Isadora users are interested by coding to do some task.
    I teach in some places, art school and professional teaching and Isadora seems yet complicated for someone who prefer to use Qlab or Millumin to do what they want. The strength of isadora is the ability to do more, to do some programming and to link data to other devices. One reason because I success to "sale" Isadora to artist and video user is this capability and the openness of the possibilities, like Max/Msp do for sound. I think the possibility to use directly code and procedure to perform what can be very difficult or even impossible in Isadora would be a great feature.
    Wait and see what the gurus will do in the future!
  • Tech Staff

    I have been looking into the possibility of creating a CEF plugin.  https://bitbucket.org/chromiumembedded/cef

    Because I also, think that this would be an incredible addition to Isadora.
    Projects like: https://github.com/atom/electron
    mix CEF and Javascript's Node framework to create a powerful development environment.
    There has been some disscussion about this within the team, and I have added feature requests, but it's a substantial task.
    Knowing the number of users that would utilize this feature would help to place it in the roadmap.

  • Yes yes very much YES! (please!)

    @j[hoepffner](/troikatronixforum/profile/15/jhoepffner) - not disputing any of that, it’s just (imo) a weigh-up of how much should be done in Isadora, and what should be kept out... where does Izzy specialise. A balance needs keeping to prevent it spiralling into a fully-fledged IDE rather than a visual construction kit (so-to-speak). Seen this with rFactor / ISI development - when you’re talking a small team of devs it can be easy for them to be stretched too thinly, and quality can suffer... that’s my only concern.