---

CSS property manager. This class is used for agnostic handling of icons, CSS class names, or styling preferences of a subsite/instance.

Defined in packages/xotcl-core/tcl/01-debug-procs.tcl

Class Relations

• class: ::nx::Object

Methods (to be applied on the object)

• class (scripted, public)

   template::CSS class [ -toolkit toolkit ] name

  In case, a mapping for CSS classes is defined, return the mapping for the provided class name. Otherwise return the input class name unmodified.

  Switches:

  -toolkit (optional)

  Parameters:

  name (required)

  Testcases:

  No testcase defined.

• classes (scripted, public)

   template::CSS classes classNames

  Map a list of CSS class names

  Parameters:

  classNames (required)

  Testcases:

  No testcase defined.

• clear (scripted, public)

   template::CSS clear

  Clear the cached toolkit name, such that it is reloads the settings on the next initialize call.

  Testcases:

  No testcase defined.

• icon_name (scripted, public)

   template::CSS icon_name filename

  Return an icon name for the proved filename Default icon name

  Parameters:

  filename (required)

  Testcases:

  No testcase defined.

• initialize (scripted, public)

   template::CSS initialize

  Initialize tailorization for CSS toolkits. The function reads the global apm package parameter and sets/resets accordingly (a) the default values (actually parameters) for the form field and (b) defines the toolkit specific CSS class name mapping. Loading optional, but universally present header files has do be performed per request... not sure this is the best place, since packages are as well initialized in the background.

  Testcases:

  No testcase defined.

• registerCSSclasses (scripted, public)

   template::CSS registerCSSclasses toolkit dict

  Register CSS class mapping for the provided framework

  Parameters:

  toolkit (required)

  dict (required)

  Testcases:

  No testcase defined.

• require_toolkit (scripted, public)

   template::CSS require_toolkit [ -css ] [ -js ]

  Make sure that the preferred toolkit is loaded. Note that some combination won't match nicely, since e.g. the toolbar of a theme based on bootstrap5 is messed up, when the preferred toolkit is bootstrap3. .... so, we should have some default setting or fallbacks to handle such situations.

  Switches:

  -css (optional)

  -js (optional)

  Testcases:

  No testcase defined.

• toolkit (scripted, public)

   template::CSS toolkit

  Return the preferred CSS toolkit

  Testcases:

  No testcase defined.

• toolkits (scripted, public)

   template::CSS toolkits

  Return the list of known toolkits

  Testcases:

  No testcase defined.

---