Opened 9 years ago
Closed 8 years ago
#14366 closed enhancement (fixed)
dojox.app Lifecycle Management
| Reported by: | Eric Wang | Owned by: | zhangyp |
|---|---|---|---|
| Priority: | high | Milestone: | 1.8 |
| Component: | DojoX App | Version: | 1.7.0 |
| Keywords: | Cc: | Dustin Machi | |
| Blocked By: | Blocking: |
Description
We need to do dojox.app application lifecycle management in application runtime because the framework/user need to do some initial/maintain works in these phase.
Current life cycle stages includes: UNKNOWN: 0, unknown STARTING: 1, starting STARTED: 2, started STOPPING: 3, stopping STOPPED: 4 stopped
Change History (5)
comment:1 Changed 9 years ago by
| Cc: | Dustin Machi added |
|---|---|
| Component: | DojoX MVC → Dojox |
| Milestone: | 1.8 → tbd |
| Owner: | changed from Ed Chatelain to zhangyp |
| Priority: | high → normal |
comment:2 Changed 9 years ago by
comment:3 Changed 8 years ago by
| Component: | Dojox → DojoX App |
|---|
comment:4 Changed 8 years ago by
it's done in dojox.app 1.8
Now dojox.app load lifecycle module by default and mixin to application main. So there's no need to add lifecycle module in the configuration file.
application life cycle has 5 status this moment: UNKNOWN,STARTING, STARTED, STOPPING, STOPPED
we only use STARTING and STARTED now. History controller should to check the application's status, if application not STARTED, History controller should not response to "popstate" event, or will application start failed on Chrome
comment:5 Changed 8 years ago by
| Milestone: | tbd → 1.8 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Shouldn't set milestone unless someone has committed to do the work for that milestone.