+

Search Tips   |   Advanced Search

The module framework


The modularization framework provides...

  • Logical points where modules can contribute data into a theme at run time
  • Optimize those contributions by combining them where possible
  • A way to enable and disable features of a theme by means of configuration, through a profile

We can turn off features not required one environment, and enable them in other environments. For example, we can disable editing capabilities in a production portal environment while enabling editing in a dev environment 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.

A module can use the Dojo Toolkit to build custom widgets. To separate code for the module from the Dojo codes, we load code in correct sequence.


See

  1. Basic artifacts and their relation
  2. Contribution types
  3. Deferred and nondeferred modules
  4. Response rendering for themes
  5. Register theme modules
  6. Debug modules
  7. Specify profile files
  8. Modules provided with the modularized theme
  9. Add or remove a ready-to-use module to a theme
  10. Capability Filters


Parent: Develop themes and skins