-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
formation ezfilter #621
Comments
I think we need to clarify what these checkboxes achieve. This story can be quick and useful if we pick good things to have checkboxes for. Or it can be a major overhaul of how we store formations, and last a couple of months. For this story, I favor the latter approach! So what should we have checkboxes for? Here's the current formations in the db:
|
(See also #493.) |
minimalist proposal: Formation:
|
I have a strong feeling here and I'm afraid you will disagree with it. My proposal would be
Expanding the list appears the full list of possible formations, which, and this is where I expect pushback but I think it's the right thing-- is the complete list of formations that jmdyck uses in The Caller's Box. I think this is correct because it gives us the complete set of possibilities, and keeps contra terminology consistent across the two major choreography repositories---while remaining simple on the surface for basic searchers. We don't need to include progression in formation (so becket* is becketcw and becket ccw but doesn't care whether it's double or single progression) because that's handled elsewhere. |
The top of the issue has been updated with the results of our textstorm. |
Current version:
Formation
Long term plan:
Adopt taxonomy in #493 as detailed in the roadmap
Archival version of this card:
Expand to be replaced by something not-a-checkbox. A bootstrap toggle? A '▶' toggler?
And the contents of that menu also to be defined.
(this is part of #563)
The text was updated successfully, but these errors were encountered: