Complete reworking of Project Logical Editor GUI/UX

If PLE UI/UX and workflow environment were to be fully optimized for everyone, but especially for people doing large amounts of scripts, customized controlled studio functions, etc… imo, it would be something like this:

  • No momentary pop-up menus that are in the way, don’t recall properly, etc.
    • A preset browser side-panel that can be left open, user always has their last browsing position at hand.
    • No pop-up menus needed for the Pre/Post Command
  • An integrated mirror of but slightly modified Key Commands/Macros browser with some additional features/function,
  • Command History and Preset Load/Execution History allows quick recycling of needed commands.
  • Cross-Comm protocols and features between PLE preset menu, key commands and macros, and post/pre commands.

The only other thing that would be needed to completely dial in the UI/UX of doing this type of stuff, is for MIDI Remote to have the ability to create Non-Graphical Devices that are just a mass trigger→command portal list… Like Generic Remote.

1 Like

I often require multiple PLE scripts daisy chained together, I came up with a whole naming convention [PLE] vs [PLEM] (macro) in their own sub-folder, in an attempt to keep my preset list organized and not choose the wrong script to run…

But in many cases, it would be better if there could be multiple PLE scripts in one PLE and I was thinking this could be achieved with the Pre/Post Command slots, being able to add an integrated additional PLE script, with a mechanism to edit it which pops up another PLE Window.

image

This would clean up my list, and make daisy chained PLE editing way easier, rather than having to switch back and forth between presets, which requires you to always be saving the presets, etc, etc.

edit

Also, this is would be a lot simpler for the average person than trying to learn the Boolean algebra parenthesis order of operation.