The plugin serves different purposes:
- Query the environment for the used theme and do the following if, and only if the theme is an instance of coon.core.Theme:
- Read out any available package configuration for the theme
- Apply the configuration to the theme and register it with the coon.core.ThemeManager
- Apply the default mode for the theme
npm install --save-dev @coon-js/extjs-plug-themeutil
npm run build:dev
for creating the dev environment.
@coon-js/extjs-link will start once the package was installed and guide you
through the process of creating symlinks to an existing ExtJS sdk installation.
This is only required if you want to run the tests (
./tests), as Siesta relies on
an existing ExtJS installation.
Theme Naming Conventions
Any theme that inherits from
coon.core.Theme that should be considered with this plugin must obey to the following
The theme must be registered, so that querying the environment via
name_of_the_theme_package, e.g. if the package's name is
theme-acme, this setting must equal to
These settings are usually configured in a file called
init.js, placed in the
overrides-folder of the theme-package.
The theme's class-name must be build as follows:
package_namespace.Theme, e.g. if the package's namespace is
acme.theme.colorTheme, the fqn of the theme-class extending
Configuring a PackageController
You are free to use this plugin in any PackageController you'd like to chose.
The following naming conventions apply:
Shorthand to be used with providing aliases
Tests are written with Siesta