Closed tmays closed 11 years ago
So, after a few days of working on span/tapemovie, and trying to actually implement the idea of combining "nodes" and "namespace", I have come BACK to the idea that the keys need to be separate. It is too complicated to refresh the namespace and rebuild it if the namespace contains the information used to rebuild itself ! (i.e. the quantity param of each node).
For the time being, I am doing the namespace creation from within tapemovie, but I think that we could generalize that function and put it into span.
I think the idea of defining "nodes" from json files is general enough to be a part of span. I have also modified the json importing function (currently in tapemovie and NOT in span) to be compatible with multiple nodes defined in the same json file.
see other issues for more on this.
What do you think?
discuss in #41
I believe we decided that in order to merge the functions of span::namespace and span::nodes so that nodes would no longer be necessary, we had to eliminate the possibility of having "aliases" to names, at least as fare as the span dict was concerned. If this is what we said, I'm going to implement this in my tapemovie2 tests and see what happens...