Confirmed users
401
edits
User:Alive/System Refactor Plan: Difference between revisions
no edit summary
No edit summary |
|||
| Line 127: | Line 127: | ||
* (Someone needs to study and discuss with me how to make this happen :) | * (Someone needs to study and discuss with me how to make this happen :) | ||
* (Otherwise it's in low priority in my queue) | * (Otherwise it's in low priority in my queue) | ||
=== Shared transition state controller in BaseUI === | |||
* '''Tracking Bug''': NaN | |||
* '''Owner''': Alive | |||
* Now all AppWindow family is using AppTransitionController as its transition state machine | |||
* Some UI modules inside system app is having their own transition controller | |||
** Listen to transitionend event with a timer | |||
** Dispatch internal events when transition starts/ends | |||
** Do certain things when transition starts/ends | |||
==== Transition Pattern ==== | |||
* I believe all transitions could be mapped to 'opened/shown', 'closing/hiding', 'closed/hidden', 'opening/showing'. | |||
* If we could make a customisable transition state machine, we don't need to re-implement it everywhere. | |||
* Another pros: We could have a AnimationManager to control all animation/transition in system app. | |||
* One more pros: We could switch to Web animation (TBD) | |||