contradb / contra

Find and share contra dances.
http://contradb.com
GNU Affero General Public License v3.0
13 stars 5 forks source link

progression #343

Open dcmorse opened 6 years ago

dcmorse commented 6 years ago

@cranhandler writes:

fear a lot of dance-enterer pushback to enter something separately that happens 'naturally,' ie, the dance enterer can look at the dance and see where progression is.

My proposal is something that minimizes the 'extra thought' burden for dance enterer. Just put the little ¶ at the bottom of the B2. If someone enters 'pass through,' the ¶ can jump up to line up with that move if someone enters 'cross trails through, ¶ jumps to line up with that if someone enters 'zig zag,' ¶ jumps up to line up with that if it's somewhere else, it's on the dance enterer to click-and-drag the ¶ to where the progression already is I like that it's wordless, it's already there in the first (presumably easy) dances you enter

if it was a 'progress then unprogress,' you can still click-and-drag the ¶ away from where it belong it's not perfect yet but I want us to think of something -mandatory (if we are doing this at all, we need to do it always) -convenient -does not add words to the caller's experience -intuitive (if possible)

Before that I wrote:

Brainstorm: Every figure gets a "progress before?" checkbox. When checked, all references to "neighbors", "gentlespoons", and "ladles" get rewritten to "next neighbors", "next gentlespoons", and "next ladles" respectively. But more importantly, contradb internally marks it as a progression. This will be invaluable to dance data-science, but the only outward sign might be putting a '¶' in front of the figure. Brainstorm2: But we need to also be able to anti-progress, as in tag-and-zag where the zig zag progresses then another zigzag antiprogresses. Or a salmon pull-buys along the set. So replace the progress checkbox with a radio: progress: +1, 0, -1.

jmdyck commented 6 years ago

Does the point of progression mean something choreographically, or is it just a way to signal a change in how to refer to people?

(I think it's a mistake to assume that every dance has a point at which it progresses, but I'm not sure if that's pertinent to this issue.)

dcmorse commented 6 years ago

Great question. It's all in the mind. It means "start thinking of these new people as your neighbors".

The current figures that progress are not well defined and really unpopular (I'm the only one that uses them, so, like, 15% of dances). It's almost like I chose an impossible user interface :grin:

cranhandler commented 6 years ago

It might actually be good if you laid out some use cases. You say 'invaluable to data science' but I'd like to hear an example or two of how you intend to gain insight from it?

On Sat, Apr 21, 2018 at 4:38 PM, Dave Morse notifications@github.com wrote:

Great question. It's all in the mind. It means "start thinking of these new people as your neighbors".

The current figures that progress are not well defined and really unpopular (I'm the only one that uses them, so, like, 15% of dances). It's almost like I chose an impossible user interface 😁

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/contradb/contra/issues/343#issuecomment-383333333, or mute the thread https://github.com/notifications/unsubscribe-auth/APbjzViTo7QqM74H2BOwxjUoR3GWYifPks5tq6bKgaJpZM4TdW3v .

-- Allison Jonjak, M.S., E.I.T. allisonjonjak@gmail.com allisonjonjak.com

dcmorse commented 6 years ago

Ideas...

  1. Search - search for dances by number of progressions - why not?
  2. Dance visualizer - after every figure, contradb renders a birds-eye-view of the dancers. To do this right, contradb needs to know who 'neighbors' refers to [this is actually planned for, like, 2019]
  3. Dance validator - if the dance editor can trace through the dance and determine that it gets you to next neighbors - then put a big happy face on it. If not: big red x. This should cut down on user error when entering dances. [this is actually planned for, like 2019]
  4. Clippy the Choreographer's Chum - have you ever written a dance and it's been great, until you get to the B2 and been like "uh, I can't make this progress". I think once you're to the B2, it should be within easy compute power for Clippy to suggest some ways to end the dance
  5. something with Markov chains and semi-random dance generation - an infinite non-repeating real time medley generator. Also automatic variation generation.
djpohly commented 6 years ago

something with Markov chains and semi-random dance generation - an infinite non-repeating real time medley generator

_HA-2_6 HA_H _ALL__G

I'd like to solve the puzzle, Pat.

cranhandler commented 6 years ago

Proposal:

dropdown includes: -add standard progression |OR| if a progression is already there, remove [current progression] -fancy progression ;;; -delete figure -duplicate figure

up 1 down 1

;;; -add double progression can put up a red 'do you really mean it?' on any move other than diagonal right left through -add reverse progression -add ladles' progression -add gentlespoons' progression