Open jamiefaye opened 1 year ago
I should add that I am most impressed with what you have done so far. Many thanks!
Shouldn't be too hard to script that from the shortcuts object. I'm just trying to decide which would be more useful: a node script to generate a cross-reference file or add a special search object (I'm trying to avoid adding a compilation step because I find it adds too much infra complexity for these kinds of weekend projects).
So I'm thinking either:
node cross-reference.js
that generates JSON or TXT or something?uses:press uses:SHIFT
. Maybe with the option to export filtered results?I would generate the X Ref entries in the browser. This should be relatively easy as the database is already there in memory. I would consider placing links everywhere I could using the # feature for local in-document destinations. Each term in a command entry could link to the XRef entry for that term, and each XRef entry would have a link-back to the original command description. You can avoid a separate build-step in the deployment script this way.
I haven't gotten all the way there, but I wanted to tweak some things before a vacation and I think I added some stuff that might be helpful to you.
This should set things up for an x ref at the UI level (and I kind of started by adding links to filtered shortcuts from the legend), but I won't be able to finish until after vacation.
It would help developers if we could generate a cross-reference table. This would be a list of each button and knob and would show all the combinations it participates in.
Something like:
X (Everything thaat uses the X knob)
Tempo (everything that uses the Tempo knob)
press (everything that involves pressing something)
(and with permutations): press (X) hold(SHIFT) etc.