#215 closed planned (done)
policy how to define commands
| Reported by: | Ichthyostega | Owned by: | Ichthyostega |
|---|---|---|---|
| Priority: | normal | Milestone: | 1alpha |
| Component: | lumieraSteam | Keywords: | interfaces session |
| Sub Tickets: | Parent Tickets: | #143, #543, #544, #561, #978, #1060, #1089, #1090, #1093 |
Description
work out a pattern how to define commands in practice. As commands are basically defined in code, this requires to understand the edit operations more in detail
Change history (18)
comment:1 by , at 2009-09-25T14:09:09Z
| blocking: | 143 |
|---|
comment:2 by , at 2009-09-25T14:40:13Z
| blocking: | → 143 |
|---|
comment:4 by , at 2010-02-22T01:10:05Z
| blocking: | 143 → 143, 543 |
|---|
comment:5 by , at 2010-02-22T01:11:22Z
| blocking: | 143, 543 → 143, 543, 544 |
|---|
comment:6 by , at 2010-02-22T01:12:16Z
| blocking: | 143, 543, 544 → 143, 543, 544, 545 |
|---|
comment:7 by , at 2010-03-05T00:19:14Z
| blocking: | 143, 543, 544, 545 → 143, 543, 544, 545, 561 |
|---|
comment:8 by , at 2015-11-28T04:38:07Z
| blockedby: | → 978 |
|---|
comment:9 by , at 2017-01-13T06:20:26Z
| blocking: | 143, 543, 544, 545, 561 → 143, 543, 544, 545, 561, 1060 |
|---|
comment:10 by , at 2017-03-10T23:35:01Z
| blocking: | 143, 543, 544, 545, 561, 1060 → 143, 543, 544, 545, 561, 1060, 1088 |
|---|
comment:11 by , at 2017-03-10T23:52:35Z
| blocking: | 143, 543, 544, 545, 561, 1060, 1088 → 143, 543, 544, 545, 561, 1060, 1088, 1089 |
|---|
comment:12 by , at 2017-03-11T00:02:57Z
| blocking: | 143, 543, 544, 545, 561, 1060, 1088, 1089 → 143, 543, 544, 545, 561, 1060, 1088, 1089, 1090 |
|---|
comment:13 by , at 2017-03-18T00:53:57Z
| Status: | new → accepted |
|---|
In the course of establishing a connection between UI and Proc-Layer, I have now created a first draft how commands are actually to be defined in practice
comment:14 by , at 2017-03-18T16:22:17Z
| blocking: | 143, 543, 544, 545, 561, 1060, 1088, 1089, 1090 → 143, 543, 544, 545, 561, 1060, 1088, 1089, 1090, 1093 |
|---|
comment:15 by , at 2017-08-10T19:25:59Z
| blocking: | 143, 543, 544, 545, 561, 1060, 1088, 1089, 1090, 1093 → 143, 543, 544, 545, 561, 1060, 1089, 1090, 1093 |
|---|
comment:16 by , at 2018-03-10T21:14:18Z
| blockedby: | 978 |
|---|---|
| blocking: | 143, 543, 544, 545, 561, 1060, 1089, 1090, 1093 → 143, 543, 544, 545, 561, 978, 1060, 1089, 1090, 1093 |
| Resolution: | → done |
| Status: | accepted → closed |
The policy established a year ago seems solid enough and adequate to get over the initial round of UI integration.
OTOH, the concept how to issue commands remains rather nebulous and needs way more implementation experience to consider it settled. So we'll go with the definition scheme for now, and consider command access as an unsolved topic for further "evolution"...
comment:17 by , at 2025-05-30T13:24:23Z
| blocking: | 143, 543, 544, 545, 561, 978, 1060, 1089, 1090, 1093 → 143, 543, 544, 561, 978, 1060, 1089, 1090, 1093 |
|---|
comment:18 by , at 2025-12-25T00:00:00Z
| blocking: | 143, 543, 544, 561, 978, 1060, 1089, 1090, 1093 |
|---|---|
| Parent Tickets: | → 143, 543, 544, 561, 978, 1060, 1089, 1090, 1093 |
Migration MasterTickets ⟼ Subtickets-plugin
Note:
See TracTickets
for help on using tickets.
(In #211) note: while this pattern is not implemented yet (9/09), I've put in the HandlingPattern::DUMMY as default, to be able to get a preliminary version of the command frontend up and running. Please search for this ticket numer in source code!