Skip to content

Special Levels: Sum-up

What are we learning here?

  • Some details of blocking layers
  • Some details of the main stage of a widget

Details of blocking in blocking stages

Blocking Messages will be used by the component core class when loading or destroying a component. In the initialization phase a blocking message will be used as splash message or in case of an error an error message will be displayed.

So you have to pay attention if you load components into a blocking layers to avoid recursive blocking.

We have learned how to load Message and Hint components into blocking layers. These two components have all splash screens by default disabled.

There are a total of four splash modules. If you want to disable splash screens of your component you can set the following namespaced options:

"@codecoupler": {
  component: {
    splash: {
      init: false,
      start: false,
      destroy: false,
      error: false

Details of loading into the base level

We want to explain a little detail of the main stage of a widget or canvas. As we have learned every component have a main stage. So also a widget or canvas component.

What we also learned is that into a stage we can load any further components. We have loaded applications into the level foreground, messages into the level block and error and hints into the level hint.

This leads to the question if we can load a component into the level base in the main stage of a widget or canvas.

Let's sketch how the structure of a widget or canvas roughly looks like:

│ Main Stage                    │
│ And outer frame DOM node      │
││ Component Element           ││
││ Accesible over this.element ││

Loading an application into the main stage (as we have done already) will be loaded by default into the level foreground. Components in this stage level do not collide with the "component element" because they are created in a separate DOM node.

Therefore they will not intercept with the compoment element. (likewise, no other component collides with the in the stage level background would be loaded).

But if you try to load a widget or canvas based component into the main stage of a widget or canvas, it would use the level base and this would collide with the component element. And this leads to an error.

You can of course load any component into another level. That would work. For example you could load a canvas based component into the level background. That would make sense. In any case, it makes no sense loading a widget or canvas based component into the level foreground.