GlowDTF Preparation

[Firionus]

• Check for bugs due to unstable ordering of Patch HashMaps (they may be the source of strange behavior where channel functions are disabled for nor apparent reason...)
  • Can confirm. Just patch a few more fixtures of two different types and you'll get invalid state
  • Possible Solutions: Change RigState to a Map, Change Patch to a List
  • I think I'll change RigState to a Map, but on Serialization change to List with fixture uuid as field
  • Then I might as well change RigState to a list with fixture uuid as field and save on some of the effort
  • Also need to update statetransition to include uuid
  • Update API docs
• Hotfix Implement Ping API (server-side) #30 and Implement Ping API (Client-Side) #31 by sending a WebSocket ping message every minute. Log it on the server.
• Sometimes Fixture Type doesn't show up when being added. Try this: Add another fixture type, add a fixture with it, go back to fixtureTypes, add Robin Esprite, observe that it only shows up in table after reload
• Another Memo in Sliders for improved performance?
  • Nah. Maybe if we create another intermediate object to speed up the useMemo comparisons we could get another performance gain. Or if we put each channel value into its own Recoil Atom, or change to MobX/Redux, we could get an improvement here.
• Don't show button for ModeMaster Dependencies when there are none
• When adding new fixtures such that the start address of a following fixture is outside the universe, the WS connection is closed and the user does not get any useful message
• When focussing a text field like Quantity on New Fixture page, you can't escape out of it with escape (likely regression from that escape bug mitigation)
• Talk to DorianSnowball
• Update Dependencies
  • Chokidar Warning when running npm update?
• Open Pull Request to check that everything works
• Rename repo to GlowDTF
• Increment FID on creation
• Clean up the __mocks__ folder - do we need it at all?
• Word Wrap in Column Layout for Fixture Types (test with Channel Layout Test GDTF and some zoom)
• Rewrite Documentation from CueGlow to GlowDTF
• Add Note that there is no security, things are only to be run in a local and protected network
• remove all references to the name CueGlow in the files (keep around in commit history)
• Document how to build and release .jar releases
• Check whether Test Ressources are in built fat jar. If yes, can we remove them to reduce size?
  • Nope, it's just 17 MB of libraries upon libraries...
• Finish ToDos in README
• Stop writing logs to a folder in the application context
• Make new PR into Working Version with Channel Function Control over Art-Net #63

[Firionus]

closed by #63