kneasle / jigsaw Goto Github PK

I can't shake how similar this looks to a Music Tracker interface. Perhaps you could draw some inspiration from them for your own GUI. I've personally been (slowly) learning renoise, which is free to play with.

Needed for first demo

• Allow frags to be:
  • moved
  • deleted
  • joined
• Allow user to set part heads
• Allow user to choose what frag gets added

Essential

• Have some kind of understanding of what methods are
• Make music highlighting depend on what proportion of parts are musical, rather than how many parts
• Adding whilst hovering a leftover row should append to the fragment
• Allow user to specify which method to add (tho not using a pie menu)
• Allow the following to be defined:
  • Methods
  • Method ruleoffs/labelled locations
  • Calls
• Allow calls to be labelled
• Allow frags to be... :
  • transposed
  • muted/soloed
  • extended
• Allow calls to be changed
• Implement group expansion for the part heads
• Add nice UI for the following:
  • Methods
  • Method ruleoffs/labelled locations
  • Calls
• Allow collapsing of leads/courses/blocks
• Allow entire state to be saved to cookie(s)

Good to have

• Have view update when transposing (but not update the undo history until the user is finished)
• Convert build script to Python
• Highlight false rows red
• Add minimap
• Display greyed-out calling positions for every call location (on both sides, and handling different calls)
• Allow Frags to be extended upwards
• Have some form of grid snapping when the user is moving fragments
• Make s snap to lead ends, and shift-S force a split wherever
• Make falseness colours stay consistent when groups are changed
• Atw indicator
• Allow user to 'tag' comp states so that they can be loaded later
• Implement pie menus
• Copy rows
• Shift-drag fragments to join them even if they don't connect (i.e. drag top row onto bottom row to update upwards, and drag bottom row to top row to update downwards)
• Switch (JS, CSS) to (TypeScript, SASS) and add the compilation to build.py
• Use a templating engine (probably Tera) to generate the HTML
• Make a proc macro to export TypeScript versions of the Derived* structs so that we get automatic type checking without having to maintain two independent copies of the same types.