Pretty much There are two big changes, and a bunch of smaller ones. The big ones are allowing for objects to expose arbitary messages (like
transform etc), and to handle pools of objects that have names (like
FluidLabelSet). Because both changes were implemented swedish chef style, they have wrought havoc on the Max and SC wrappers (which have bloated as a result), and changed the API for objects in some messy ways. The plan is to refactor out some of this badness before doing the PD and CLI stuff.
With that said , I’ll do some gratuitous speculation:
- the whole business of named objects doesn’t obtain in the CLI context: a ‘dataset’ will have to be a file, and – in the first instance at least – I imagine chaining together operations will be done through shell scripting.
- The messages is a more interesting one, but (off the top of my head), something like the
git convention of
git <verb> would be the way, e.g.
FluidKDTree knearest --model myfitttedtree.json --data somedatapoint.csv