Pia Baltazar
Pia Baltazar
> I am afraid it is 400% unclear and looks as if the attribute was misused from its intended purpose. OK, I guess we need to have a little storytime...
OK, done! https://github.com/OSSIA/libossia/commit/da048bb2407d7c600336ac958e0d7f239f11946d Is there anything else that requires keeping the issue open ?
what do you think it should be ?
I’m not 100% sure, but my gut feeling is that it shouldn’t be different, since a [ossia.remote] can be under an [ossia.client], which would then communicate through OSCquery to the...
I'm not sure we should use [j.namespace] as a model, it was quite complicated, maybe even a bit convoluted... it worked by creating and combining filters, e.g. ```filter/set eqViews object...
but, yeah, maybe an [ossia.namespace] (or maybe rather [ossia.explore], [ossia.browse] or [ossia.explorer] ???) would be a better idea specification hypotheses: - when placed under a device (including the global device)...
also, we could add an attribute per parameter's attribute, e.g. - ```@name (nothing provided)``` will return all nodes under the provided address - ```@name ant{oine,hology}``` will return all nodes only...
> Something that would be good being able to do is what we use to do with [j.receive model:address]. Being able to get the parent model address. Maybe that could...
> When working with j.namespace something also used in quite some Jamoma models was being to output a full namespace or only model or attribute nodes. we could do that...