Partial action wish (and non-wish) list #145

Open
opened 2026-05-30 16:57:23 +00:00 by glen · 1 comment
Owner

This issue is to maintain the information from closed #132 that was not acted on: primarily the following checklist of things we do eventually want to have actions for but don't yet, but also some items we don't see a need for as actions.

  • Remove an entity from the assembly
  • Save the assembly
  • Clear the assembly
  • Load an assembly (does this necessarily invoke the "clear" action? Or should it be possible to load an assembly into a non-empty assembly, adding more elements? What happens in the case of elements with the same id as existing ones, then?)
  • Manipulate the selection (add/remove entities from it, or change what is selected wholesale)
  • Change what view is focused
  • Export the assembly and/or snapshot a view in any of various formats

Things we don't necessarily think need to be implemented as actions under the current design vision: close an assembly or open/handle multiple assemblies.

This issue is to maintain the information from closed #132 that was not acted on: primarily the following checklist of things we do eventually want to have actions for but don't yet, but also some items we don't see a need for as actions. - [ ] Remove an entity from the assembly - [ ] Save the assembly - [ ] Clear the assembly - [ ] Load an assembly (does this necessarily invoke the "clear" action? Or should it be possible to load an assembly into a non-empty assembly, adding more elements? What happens in the case of elements with the same id as existing ones, then?) - [ ] Manipulate the selection (add/remove entities from it, or change what is selected wholesale) - [ ] Change what view is focused - [ ] Export the assembly and/or snapshot a view in any of various formats Things we don't necessarily think need to be implemented as actions under the current design vision: close an assembly or open/handle multiple assemblies.
Author
Owner

Another point from #132 worth remembering is that we may need categories of actions to allow for filtering the command listener; for example if "setfocus" is an action and it is happening a lot as you click around, you may not want to see all of those actions in the listener.

Another point from #132 worth remembering is that we may need categories of actions to allow for filtering the command listener; for example if "setfocus" is an action and it is happening a lot as you click around, you may not want to see all of those actions in the listener.
Sign in to join this conversation.
No description provided.