dcmorse
commented
6 years ago Yeah, agree that this is needed. It blew up in complexity towards the end of the dialect project and I cut it. I don't think there's an issue for it yet.
I'd also like to support "turn by the (right|left) shoulder", which would be in the menus as "turn by the shoulder".
The tricky thing is having a UI name separate from the thing that gets rendered in the figure string.
Hey, what about a rewrite of dialects where we could have advanced move substitutions, and it'd look something like:
gyre -> menu as 'turn by the shoulder' and format as '$who turn by the
$direction shoulder'
This isn't the only affected figure. Renames of zig zag and allemande orbit have no effect in rendered figure text, because those words don't actually appear in the figure text. If you want to see the words "giz" and "gaz" in your figures instead of "zig" and "zag", you're out of luck.
There's enough here to make a little domain specific language. It'd be hard for a user to understand, but they're not the only customers. There are hundreds of lines devoted to writing these strings in javascript, and if there were a more succinct language it'd simplify that file too.
hm.
cranhandler
My preferred dialect, and one that I expect will be quit common, is replacing 'gyre' with 'right shoulder round' | 'left shoulder round'.
Currently, because libfigure knows the figure as gyre which is modified by right or left, my dialect substitution of 'shoulder round' results in dances rendering
'shoulder round left shoulder' or 'shoulder round right shoulder' whereas I would prefer 'left shoulder round' or 'right shoulder round'
Is there a convenient way we can add a selector that lets me indicate (for my dialect) whether the right/left modifier displays before or after the figure name?
Example dance: http://contradb.com/dances/375
currently using: gyre
currently using: shoulder round