There should be a way to have "fixed" tuples

ossia / score

ossia score, an interactive sequencer for the intermedia arts

https://ossia.io

Other

1.5k stars 104 forks source link

There should be a way to have "fixed" tuples #356

Open jcelerier opened 7 years ago

jcelerier commented 7 years ago

e.g. always [int, float] or [int, int, int]

bltzr commented 7 years ago

is that fixed with Vec2f or so ? @jcelerier

jcelerier commented 7 years ago

mhh, not really. The problem is fitting with the osc & oscquery specification where for instance a node is said to have type [int float int float string string] (for instance) and cannot deviate for it. while the tuples in libossia / i-score can add / remove elements and have their elements change type.

bltzr commented 7 years ago

OK, then from the UX POV, I guess there could be a number field for the number of items (in case of Tuple type) then, a kind of « subpanel » for setting each element (or maybe just a list of types as a start)

but I guess there’s some work to be done under the hood first...

gsenna commented 6 years ago

Just to say that for my use case I'm fine with some way of creating list nodes with a fixed number of parameters whose types are set at the beginning.

bltzr commented 6 years ago

so, doing that would imply separating the list type into 2 different types, right ?

list : would stay the same, i.e. just a bucket for putting whatever one likes into it (just like the generic type in Jamoma - there would be no way in score (as is currently the case) to set domains or range (BTW, then the clipmode could be just removed)
tuple : would be a new type, with a fixed number of members, each of them being of a fixed (and unmutable) type - then we could make a dedicated parameter editor window, possibly with tabs for each member, as @gsenna suggested, where we would basically have all attributes (or just some ? at least range... what else ?) that we can find for a mono-dimensional parameter

I've added an issue for that in libossia, as I guess that would be the first step towards this: https://github.com/OSSIA/libossia/issues/403

jcelerier commented 6 years ago

list : would stay the same, i.e. just a bucket for putting whatever one likes into it (just like the generic type in Jamoma - there would be no way in score (as is currently the case) to set domains or range (BTW, then the clipmode could be just removed)

actually there is a domain / range, it's just that it isn't shown in the UI...

Also this would be nice since it would map more closely to the OSC and OSCQuery semantics

jcelerier commented 6 years ago