there is no reason to keep dock actions in class side #22

Open
opened 2025-10-29 08:51:47 +01:00 by estebanlm · 0 comments
Owner

is less flexible as a mechanism, and the same thing could be managed instance-side now.
I propose to do a revamp or all that mechanism, to

  • move all remaining actions to SpAction or alike (remove PvAction infra)
  • move actions and action group definition to class side
  • add a "duplication shortcut validation" mechanism to be added in the collection of actions stage, as a last step
is less flexible as a mechanism, and the same thing could be managed instance-side now. I propose to do a revamp or all that mechanism, to - [x] move all remaining actions to SpAction or alike (remove PvAction infra) - [x] move actions and action group definition to class side - [ ] add a "duplication shortcut validation" mechanism to be added in the collection of actions stage, as a last step
estebanlm added this to the alpha2 milestone 2025-10-29 08:51:48 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pharo/Pulsar#22
No description provided.