#1145 closed meta (done)
define startup sequence
| Reported by: | Ichthyostega | Owned by: | Ichthyostega |
|---|---|---|---|
| Priority: | normal | Milestone: | 0integration |
| Component: | lumiera | Keywords: | integration roadmap architecture design |
| Sub Tickets: | Parent Tickets: | #333, #1044, #1146, #1147, #1148, #1149, #1150, #1169, #1416 |
Description (last modified by )
We need a general plan how the application boots up into working state
- Foundation is the framework of subsystems (which is basically in place by now)
- the subsystem life-cycle defines how the root of each part boots up as an independent entity
- each part then has to define its local path towards readiness for service
- the UI has to bring up an empty UI frame
- the session need to establish and maybe populate its structures
- the vault will start and wire its operating entities
- we need to define some cross-connecting and install asynchronous listeners
- beyond that point we get some leading entity, either
- the UI
- a script runner
- a network connector
The task for this ticket is to investigate all those concerns and to document what has to be defined.
Change history (14)
comment:1 by , at 2018-07-12T18:08:51Z
| blocking: | 333 → 333, 1146 |
|---|
comment:2 by , at 2018-07-12T18:10:20Z
| blocking: | 333, 1146 → 333, 1146, 1044 |
|---|
comment:3 by , at 2018-07-12T18:13:01Z
| blocking: | 333, 1146, 1044 → 333, 1044, 1146, 1147 |
|---|
comment:4 by , at 2018-07-12T18:29:54Z
| blocking: | 333, 1044, 1146, 1147 → 333, 1044, 1146, 1147, 1148 |
|---|
comment:5 by , at 2018-07-12T18:38:44Z
| blocking: | 333, 1044, 1146, 1147, 1148 → 333, 1044, 1146, 1147, 1148, 1149 |
|---|
comment:6 by , at 2018-07-12T18:50:36Z
| blocking: | 333, 1044, 1146, 1147, 1148, 1149 → 333, 1044, 1146, 1147, 1148, 1149, 1150 |
|---|
comment:7 by , at 2018-07-15T13:20:22Z
| Owner: | set to |
|---|---|
| Status: | new → accepted |
comment:8 by , at 2018-07-28T13:10:30Z
the situation here is now that I hat to read some code and search for various bits of information here and there, just to come to the conclusion that mostly this topic is kind-of settled. But it is hard to find out what is really settled and what needs doing. So the core task for this ticket is now to put together a new page in the "design" section of the lumiera website (documentation). There is a page describing the subsystems and lifecycle events. But in the architecture section, there is just a preliminary draft page with some of the initial ideas. And in fact this would be the right place for exhaustive documentation...
comment:9 by , at 2018-09-24T00:21:24Z
| blocking: | 333, 1044, 1146, 1147, 1148, 1149, 1150 → 333, 1044, 1146, 1147, 1148, 1149, 1150, 1169 |
|---|
comment:10 by , at 2020-02-22T22:20:09Z
The mentioned docomentation page is in place since some time. It defines the meaning of the term »Subsystem« and it has a complete listing of Lumiera's Lifecycle phases. The descriptions for the individual Subsystems are missing, though.
TODO: fill in the description for Session and GUI (since that is what we know currently)
comment:11 by , at 2020-02-23T07:24:22Z
| Resolution: | → done |
|---|---|
| Status: | accepted → closed |
pfff...
writing text is hard
comment:12 by , at 2022-10-21T20:52:38Z
| Description: | modified (diff) |
|---|---|
| Priority: | urgent → normal |
comment:13 by , at 2025-12-25T00:00:00Z
| blocking: | 333, 1044, 1146, 1147, 1148, 1149, 1150, 1169 |
|---|---|
| Parent Tickets: | → 333, 1044, 1146, 1147, 1148, 1149, 1150, 1169 |
Migration MasterTickets ⟼ Subtickets-plugin
comment:14 by , at 2026-03-03T02:54:11Z
| Parent Tickets: | 333, 1044, 1146, 1147, 1148, 1149, 1150, 1169 → 333, 1044, 1146, 1147, 1148, 1149, 1150, 1169, 1416 |
|---|
Attach to parent #1416 (clarify lifecycle of the »Vessel«).
obviously working on that since some days, mostly conceptual work though