Done a lot of work on span/tapemovie the last few days. I've have kept span clear of specific tapemovie things, but added a few keys and functions to the environment.
added "hardkeys" and "softkeys" to make it easier to reset (erase) and re-create the span dict without having to run a low-level "span/load which would unnecessarily re-create everything. (see issue #43)
wrote a more sophisticated projectstructure interpretation routing and syntax, allowing us to easily write whatever we want of span to the project, including the projectstructure itself. (issue #42)
made a new clippings object called dict.dump which greatly simplifies dict merging - just use "replace" to write all keys to the dict to merge to, and the keys will be created if they don't already exist. The current clippings object can handle 10 sublevels of hierachy, but more can easily be added.
modified datetimestamp clipping to be usable with all three stamps : created, opened, saved
incorporated "inserts" into span/load chain so that tapemovie or something else can be integrated into the process seamlessly. This does not change span/load at all if there are no inserted functions. We can definitely discuss this, as we can ALL of my recent proposals/advances, though it seems very fluid and functional to me.
Also, proposed that we really DO need a separate "nodes" and "namespace" key, so that a namespace can be rebuilt from the nodes key (difficult to rebuild from data within itself...). For now, the nodes files are read from the tapemovie patch (tm.span), but I do believe that there could be eventually some way of generalizing the nodes file reading and namespace building format so that these things could be directly incorporated into span.
added a simple but cool nodes quantity editor inside of the tapemovie dev patch (tapemovie2-prealpha-test2). It writes automatically to the projectfile.
added "replace" and "remove" functions to span.requests
added project::name key, just to make it easier to get the name whenever we want. The name is still generated by stripping off the path, but keeping one level of hierachy above projectfile like we did in tapemovie.
That's all I can think of now. I hope there's nothing I did that messes things up for you, but regardless, we can talk about all of it...
Done a lot of work on span/tapemovie the last few days. I've have kept span clear of specific tapemovie things, but added a few keys and functions to the environment.
added "hardkeys" and "softkeys" to make it easier to reset (erase) and re-create the span dict without having to run a low-level "span/load which would unnecessarily re-create everything. (see issue #43)
wrote a more sophisticated projectstructure interpretation routing and syntax, allowing us to easily write whatever we want of span to the project, including the projectstructure itself. (issue #42)
made a new clippings object called dict.dump which greatly simplifies dict merging - just use "replace" to write all keys to the dict to merge to, and the keys will be created if they don't already exist. The current clippings object can handle 10 sublevels of hierachy, but more can easily be added.
modified datetimestamp clipping to be usable with all three stamps : created, opened, saved
incorporated "inserts" into span/load chain so that tapemovie or something else can be integrated into the process seamlessly. This does not change span/load at all if there are no inserted functions. We can definitely discuss this, as we can ALL of my recent proposals/advances, though it seems very fluid and functional to me.
Also, proposed that we really DO need a separate "nodes" and "namespace" key, so that a namespace can be rebuilt from the nodes key (difficult to rebuild from data within itself...). For now, the nodes files are read from the tapemovie patch (tm.span), but I do believe that there could be eventually some way of generalizing the nodes file reading and namespace building format so that these things could be directly incorporated into span.
added a simple but cool nodes quantity editor inside of the tapemovie dev patch (tapemovie2-prealpha-test2). It writes automatically to the projectfile.
added "replace" and "remove" functions to span.requests
added project::name key, just to make it easier to get the name whenever we want. The name is still generated by stripping off the path, but keeping one level of hierachy above projectfile like we did in tapemovie.
That's all I can think of now. I hope there's nothing I did that messes things up for you, but regardless, we can talk about all of it...
-t