> > - how do you get the message to the canvas (message bus or special > > object?) > > an advantage of an object could be an outlet giving some feedback > after doing a modification. i.e. it could output the uuid of the > last created object. > otherwise i see no dis/advantage about message bus vs. object do you? > > i think it's nice to have a similar syntax or at least similar > wording as a patch file is written. > > in pd the msgs for dynamic patching are very close to patching with > the mouse (i belive).
when doing dynamic patching, one would want to pass certain information to the engine: - name - argument list - attributes (when they are used in future) - gui data (like position) attributes and gui data is basically optional, though ... > > - how do you reference objects in a patch (pd uses integer indexes, > > which are very fragile, dyn~ uses symbolic names, which it maintains > > itself, nova internally uses uuids, but i doubt you would want to use > > them for dynamic patching) i guess, using symbolic names as references is the only reasonably powerful way ... but where should they be visible? can names be shared in different patches? i would say, the symbolic name resolution should be local to one dynamic patching interface (like one instance of a |thiscanvas| object) ... maybe this object can even be written like a normal nova class and working similar as |dyn~|, which solves the problem by not allowing direct access to the pd canvas, but encapsulating it in a managed sandbox canvas. having symbolic names, which are unique and local to a canvas (or a patch) would be another way ... ... i have to think about some of the details ... but i hope, i'll come up with a solution in the next few weeks ... cheers, tim -- [EMAIL PROTECTED] ICQ: 96771783 http://tim.klingt.org Your mind will answer most questions if you learn to relax and wait for the answer. William S. Burroughs
signature.asc
Description: This is a digitally signed message part
_______________________________________________ nova-dev mailing list [email protected] http://klingt.org/cgi-bin/mailman/listinfo/nova-dev http://tim.klingt.org/nova
