Topic/minor

[LFSaw]

really minor stuff...

[LFSaw]

should be merged into musikinformatik/Steno

[LFSaw]

(from the other, now due to repository moving removed discussion):

We all have different taste, it seems :)

Tbh., I find \synthIndex, \index, and \nestingDepth not semantically valid enough to justify their length.
I tried to find abbreviations that are, what I thought, either common (\fb, \idx), or follow a common scheme. It seems I failed :)

Since Steno is a livecoding environment, I think it'd be great to have reasonably short yet meaningful names. For an upcoming show, I'll have 10min to create something with Steno and I'd like to spend that time with expressing what I want rather than searching for the right keys (on my keyboard/in the dict) :)

here are proposals:

indexing

I think i and j are valid alternatives, although it is difficult to deduct from them which one has which meaning:

1. running index in the sequence of all synths (currently called \synthIndex), vs.
2. running index in the sequence of synths of current type (currently called \index)

Since j is often used nested within a loop using i, my "Eselbrücke" could be i represents more cases (case 1.) than j (case 2.).

I could also imagine \pos as a replacement for \synthIndex, since it is (almost) the position in the string...

nestingDepth

I think \depth would be sufficient.

numChannels

\numChans ?

[telephon]

We all have different taste, it seems :)

maybe! I also change it sometimes. Is idx used a lot in some world specifically?

Tbh., I find \synthIndex, \index, and \nestingDepth not semantically valid enough to justify their length.

Yes, you are completely right. They (or their equivalents) should also be methods of the StenoSignal object, then one gets autocompletion.

[telephon]

numChans

I don't think it's worth those few letters.

pos

yes, maybe pos and slot? Or pos and i?

depth

yes, depthnitely.

[telephon]

We could use this conversation to discuss what information we could pass to the synth / settings about the syntactic context.

1. simple character count (possibly omitting spaces, parentheses, etc. and "!")
2. synth count, the howmanyth synth it is
3. depth, how deep in the total bracket stack (both [] and (), and {})
4. local character count in the bracket context
5. local synth count, howmanyth synth in the bracket context
6. layer count, howmanyth layer in next outermost parallel