Confirmed users
401
edits
No edit summary |
|||
Line 35: | Line 35: | ||
=== Stage.2 - Architecture love === | === Stage.2 - Architecture love === | ||
==== Find out loading sequence and dependency relationships ==== | |||
==== Do architecture review and rework case by case ==== | |||
# Find the unnecessary module coupling and remove it. | |||
# Split a single "heavy-loading" module into different modules with its specific responsibility | |||
## For instance, split window manager into 3 pieces: manager, factory, and classes. | |||
# Move the static DOM elements into its responsible module and let the module render its own UI with whatever template engine. | |||
# (optional) Use event emitter to replace DOM elements. (But we need to find out 'home' event replacement.) | |||
# Find out patterns and figure out if we could group them. | |||
## For example many modules are depending on a specific settings to be ON/OFF. Maybe we could lazy load them in a SettingsOberver. | |||
Some candidate bugs | ==== Some candidate bugs ==== | ||
# Clean widget-like cost control | # Clean widget-like cost control | ||
# Clean rocketbar | # Clean rocketbar |