Command definition registration
Establish the concrete procedures
- at which place to put the command scripts
- how to drive registration of those scripts at start-up of the Session subsystem
Change history
(8)
| blockedby: |
215, 300, 184 → 184, 215, 300
|
| blocking: |
1087, 144 → 144, 1087
|
| Description: |
modified (diff)
|
| blocking: |
144, 1087 → 144, 1087, 1092
|
| Owner: |
set to Ichthyostega
|
| Status: |
new → accepted
|
| blockedby: |
184, 215, 300 → 184, 215, 300, 1093
|
| blocking: |
144, 1087, 1092 → 144, 1087, 1092, 1095
|
| blockedby: |
184, 215, 300, 1093 → 184, 215, 300
|
| blocking: |
144, 1087, 1092, 1095 → 144, 1087, 1092, 1095, 1093
|
| Resolution: |
→ done
|
| Status: |
accepted → closed
|
| blockedby: |
184, 215, 300 → 184, 300
|
| blocking: |
144, 1087, 1092, 1095, 1093 → 144, 1087, 1092, 1093, 1095
|
| blocking: |
144, 1087, 1092, 1093, 1095 → 144, 1087, 1092, 1093, 1095, 1103
|
| blockedby: |
184, 300
|
| blocking: |
144, 1087, 1092, 1093, 1095, 1103
|
| Parent Tickets: |
→ 144, 1087, 1092, 1093, 1095, 1103
|
| Sub Tickets: |
→ 184, 300
|
While building the UI backbone, defining the command lifecycle became a necessity, and thus this topic can not be further postponed -- which is a bit problematic, since I know near nothing regarding what commands actually need to do.... anyway, whatever