zachberry / vidkid Goto Github PK

Want to be able to transition between two or more complete visualizations. Thinking either this could be done in the existing interface with nodes representing scenes (Perhaps these are composite nodes - #10 ) or there could be a different UI geared towards performance, where different scenes could be switched between

Another option: https://github.com/localForage/localForage

Want to be able to zoom in and out of the edit view. The basics of this are in but commented out as it needs more work.

React code is a mix of

1. Events
2. Specific props passed to children
3. Whole classes (docState) passed to children

Thinking you could select a [?] button in the toolbar and then hover over items to get a tooltip

Spoke with someone on the Edge dev team who gave me some options to get around having to create elements with a datestamp, like <n1-12345678>.

1. There is an unregisterComponent. When editing a node I should be able to unregister, then re-register. For some reason I missed this in the docs when working on this.
2. The various lifecycle methods (onAttrChanged, onRemove, etc) could call another method. That way I wouldn't need to unregister then re-register, instead the user would be updating a method that the native web component would call. However this would introduce a second function call.

DocState and NodeMap really need some tests!

Would like to create a node which itself is a map of nodes.

Idea would be that you could somehow double click on a node to edit it. A composite node could have an Inner Edge and Outer Edge node defining the inputs and outputs, or a custom UI to somehow indicate these.

Edit mode can reduce to a crawl very quickly and it mostly has to do (I think) with too many react re-renders happening. Perhaps there could be a mode to update input values once a second instead of as soon as they change, reducing the react render party.

Want to be able to have the user cherry-pick different inputs to place a copy of them in a left-hand bar. That bar could show up in performance mode. That way you could create a custom set of values that you care about which would control the scene (and leave out the noise of the node map). That solves a problem the node controls are out of reach once inside performance mode.

Toggling preview fixes it

• - Tag items by type (Hardware, Screen, etc)
• - Have an 'about' for each item