The module framework allows
extensions to contribute to different areas of a page to provide flexibility,
enhance the user experience, and maximize performance.
The framework provides logical points where modules can contribute data into a theme at run time and to optimize those contributions by combining them where possible. This framework allows multiple disparate remote sources to be combined into one request for greater performance.
It also provides a way to enable and disable features of a theme by means of configuration, through a profile. You can spend your time focusing on the interface design of the theme without being concerned about the details of how to get features to work correctly within their theme. It also provides them an easy way of turning off features that they do not need in one environment that they might use in another environment.
For example, you can disable editing capabilities in a production portal environment while enabling them in a development environment. The same theme code can be used across such environments where the only variable is the module inclusion profile.
Modules are registered extensions and then consumed by a module profile. Each module is enumerated by the modules unique identifiers. Modules might require other modules to allow the automatic inclusion of necessary code required to make a particular feature work.
The framework provides logical points where modules can contribute data into a theme at run time and to optimize those contributions by combining them where possible. This framework allows multiple disparate remote sources to be combined into one request for greater performance.
It also provides a way to enable and disable features of a theme by means of configuration, through a profile. You can spend your time focusing on the interface design of the theme without being concerned about the details of how to get features to work correctly within their theme. It also provides them an easy way of turning off features that they do not need in one environment that they might use in another environment.
For example, you can disable editing capabilities in a production portal environment while enabling them in a development environment. The same theme code can be used across such environments where the only variable is the module inclusion profile.
Modules are registered extensions and then consumed by a module profile. Each module is enumerated by the modules unique identifiers. Modules might require other modules to allow the automatic inclusion of necessary code required to make a particular feature work.
The module framework allows a profile to specify whether to defer a
particular module. By default, a module is loaded when the initial page
loads, but modules that are specified as deferred modules are loaded
after the page loads.
Nondeferred modules are enabled whenever a request for a page is made to the portal servlet resulting in a full page refresh. Use a client-side JavaScript module to load resources associated with deferred modules on demand. For example, load deferred modules when entering edit mode for a page. Resources that are not required in view mode can be lazy loaded when the page mode is changed to edit.
Nondeferred modules are enabled whenever a request for a page is made to the portal servlet resulting in a full page refresh. Use a client-side JavaScript module to load resources associated with deferred modules on demand. For example, load deferred modules when entering edit mode for a page. Resources that are not required in view mode can be lazy loaded when the page mode is changed to edit.
No comments:
Post a Comment