update shell
This commit is contained in:
@@ -79,6 +79,7 @@ The exact event catalog may evolve incrementally.
|
||||
Illustrative baseline categories include:
|
||||
|
||||
- project lifecycle events;
|
||||
- project loading lifecycle events;
|
||||
- workspace selection events;
|
||||
- run and build intent events;
|
||||
- activity publication events;
|
||||
@@ -86,6 +87,20 @@ Illustrative baseline categories include:
|
||||
- diagnostics update events;
|
||||
- asset selection events.
|
||||
|
||||
For project bootstrap and splash/loading integration, the Studio event catalog should reserve typed events for:
|
||||
|
||||
- project loading started;
|
||||
- project loading progress;
|
||||
- project loading completed;
|
||||
- project loading failed.
|
||||
|
||||
Project loading progress events should carry at least:
|
||||
|
||||
- the project identity,
|
||||
- a typed loading phase,
|
||||
- a user-facing status message,
|
||||
- and either determinate progress or an explicit indeterminate marker.
|
||||
|
||||
## Theme and i18n Compatibility
|
||||
|
||||
Shared Studio UI foundations must preserve:
|
||||
|
||||
Reference in New Issue
Block a user