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

dot2slash problem #77

Closed reno- closed 10 years ago

reno- commented 10 years ago

I work with a dot namespace, (node.1/param ) and it seems to be impossible to be compatible with the dot2slash abstraction. The dot2slash converts the node.1/param into a node/1/param in the namespace.

The problem is when I create and play a cue, it will request and send to node/1/param.

I guess dot2slash need is a backwards-compatibility option for working with tapemovie project, but I guess a sepearate updater for tapemovie project into span project must exists aside span core.

And for my node.1/param, it works like a charm if I remove the dot2slash from all span.param.int/dec/string etc…

Any opinion Tom?

reno- commented 10 years ago

I'm talking about the dot2slash abs which is in all span.param.dec/int etc....

tmays commented 10 years ago

That's probably because the idea is that the namespace works with node::instance::param

There is never a node.instance in the namespace. That doesn't stop us from using node.instance in editors and events. The system param that we established chooses the global mode of either node.instance or node/instance

So I don't know if you're trying to do something in a non expected way, or just not the "right" way. But For me this stuff is working fine... -tom

On 16 nov. 2013, at 12:12, reno- notifications@github.com wrote:

I'm talking about the dot2slash abs which is in all span.param.dec/int etc....

— Reply to this email directly or view it on GitHub.

reno- commented 10 years ago

I work in a node.instance style for years, and I just want to keep this habit. From what I remember, we can use span in both ways.

I just have a problem With dot2slash abs in params because it translate a node.instance into a node/instance but no conversion ok the other side.

So If I want to use node.instance, span could just record this node as node.instance.

I will be in France next week, maybe a 5 minutes talk should make a misunderstood disappear,

Cheers !!

Renaud

Le 16 nov. 2013 à 13:42, tmays notifications@github.com a écrit :

That's probably because the idea is that the namespace works with node::instance::param

There is never a node.instance in the namespace. That doesn't stop us from using node.instance in editors and events. The system param that we established chooses the global mode of either node.instance or node/instance

So I don't know if you're trying to do something in a non expected way, or just not the "right" way. But For me this stuff is working fine... -tom

On 16 nov. 2013, at 12:12, reno- notifications@github.com wrote:

I'm talking about the dot2slash abs which is in all span.param.dec/int etc....

— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.

tmays commented 10 years ago

Yes, with the addition of system::data::events::format we can make all params work in either .instance or /instance format. The "dot2slash" patcher isn't there in params to access the namespace in slash mode, but just to be able convert to "::" to access the namespace.

Maybe you're wanting to create your actual namespace with .instance? If this is what you're wanting, I think this would throw a wrench into the whole span namespace format that we established, and overly complicate things.

If your system::data::events::format is 1, then all events and params work in .instance mode, and this should be all you need to use .instance in events and send/receives.

Unless, of course, there's something I'm not getting...

reno- commented 10 years ago

If your system::data::events::format is 1, then all events and params work in .instance mode, and this should be all you need to use .instance in events and send/receives.

This is the part I didn't know/remember.

Thanks to point me on it.

Best,

Renaud