Ticket #144 (accepted meta)
Proc Command handling frontend
| Reported by: | ichthyo | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 1alpha |
| Component: | lumiera | Keywords: | meta interfaces |
| Cc: | Blocked By: | #146, #148, #184, #205, #208, #210, #266, #269, #300, #301 | |
| Blocking: | #143, #191 |
Description (last modified by ichthyo) (diff)
Command handling within Proc-Layer can be seen as a frontent for invoking commands and a backend integrated with the UNDO manager, serialiser and session persistent storage. While the command backend (Serialiser) can remain unimplemented until alpha, we urgently need the frontend and especially how command definition works in order to get ahead on the Proc/GUI interfafce.
Change History
comment:1 Changed 3 years ago by ichthyo
- Owner set to ichthyo
- Priority changed from normal to urgent
- Status changed from new to accepted
- Milestone set to 0integration
comment:15 Changed 2 years ago by ichthyo
- Blocked By 300 removed
(In #300) Now able to define commands, access them by ID and invoke the operation.
comment:17 Changed 2 years ago by ichthyo
- Description modified (diff)
- Blocked By 300 added
- Priority changed from urgent to normal
- Owner ichthyo deleted
- Milestone changed from 0integration to 1alpha
- Keywords meta interfaces added
- Type changed from todo to planned
- Blocking 326 removed
After having a running implementation of this command handling frontent, implementing it up to full functionality can be retargeted to the Alpha phase, when we work on actually storing session data persistently. This ticket has meanwhile evolved into a tracking/meta-ticket; thus I'll drop ownership.
effectively working on this one since last week, concept draft turned out OK, but some facilities are missing. I'll defer most of the actual implementation (see blocking sub-Tickets) once the outline of the interface is done