Confirmed users
502
edits
Gaia/Settings/docs: Difference between revisions
→Start Up Path
(→Module) |
|||
| Line 7: | Line 7: | ||
A panel can be associated with an AMD module implementing a specified interface. In the module we can then require other necessary modules that are used in the panel. | A panel can be associated with an AMD module implementing a specified interface. In the module we can then require other necessary modules that are used in the panel. | ||
=== Start Up Path === | === Start Up Path === | ||
To present the visuals as | To present the visuals as fast as possible, we determine the first panel to be displayed and then append the HTML elements of the panel to the DOM tree. Note that at this time the panel is visible but still not interactive because the associated modules of the panel are not loaded yet. | ||
There can be a short gap between the panel being presented and all fundamental modules loaded. The time results from loading and initializing requirejs. '''InitialPanelHandler''' was introduced to provide basic interactions until the associated modules get loaded. One can provide their own panel handler if the required interactions are beyond what '''InitialPanelHandler''' can provide. | There can be a short gap between the panel being presented and all fundamental modules loaded. The time results from loading and initializing requirejs. '''InitialPanelHandler''' was introduced to provide basic interactions until the associated modules get loaded. One can provide their own panel handler if the required interactions are beyond what '''InitialPanelHandler''' can provide. | ||