search

didascalie-net / span

Spaces And Nodes - Environnement for real time media controls and organisation
didascalie-net.github.com/span
3 stars 0 forks source link

node key and node files (json) #41

Closed tmays closed 11 years ago

tmays commented 12 years ago

I've been working on creating the nodes key for tapemovie, and as I said in the last issue, I think that the nodes key functions can be generalized for span. The idea is, as we determined before, that we read the json files in the nodes or modules folder that we define, and that is what fills the nodes key in span dict. The original importing function that I put into the tapemovie dev patch read in each json file and used the name of the file as the name of the node. This made it impossible to include more than one node in a json. I modified the json structure for the nodes so that a json nodes file contains a key of the name of the node (module). That means that several nodes (modules) could possibly be defined from within the same json file. That is especially interesting to define nodes that are not necessarily attached to patches that need to be loaded (modules).

The patch tapemovie2/sdk/module-makejson4.maxpat has been changed to reflect this. It takes the .txt node definition file and converts it to json with an initial key of the name of the node.

I have removed the "alias" parameter from the node (module) name. This greatly simplifies working with the namespace and the nodespace. I hope you agree with this.

For now, I have kept the alias for the parameter names, but I'm not sure if we should or not.

Basically, if we want to customize un environment, we change the contents of the node json files.

In the "near" future, we should think about a powerful alias function for nodes and parameters that doesn't actually change the key names of the namespace.

As I said in the previous issue, I have gone back to the idea that there should be a node key in span separate from the namespace key. This makes it MUCH easier to rebuild the namespace because it is based on information NOT found in itself.

Also, if span is "spaces and nodes", it makes sense that there be a namespace key AND a nodes key, right?

What do yo think?

reno- commented 11 years ago

There is a lot of way to declare instance /1/vol/del /del/1/vol /circ/1 /layer.1/alpha /modul8/alpha/1

so nodes will stay outside span. span just know namespace.

reno- commented 11 years ago

We need to found exemples and think about it for the next workshop

reno- commented 11 years ago

From now, we will support only /Node.1/param and /Node/1/param. because span namespace is done to have a slash under each node. So its native language should be /Node/1/Param