Documentation
Primary version
Primary version
  • Cubbles documentation
  • First steps
    • Generate a project
    • Create a webpackage
    • Create an elementary component
    • Create a compound component
      • Compound slot initialization
  • Runtime extension - RTE
    • User guide
      • RTE Integration
      • The Cubbles TAG API
        • The Cubbles Dependency API
      • The Cubbles Javascript API
        • Interacting with Cubbles from the outside
        • Adding dynamic connections
        • Interacting with Elementary Cubbles from the inside
      • The RTE Processing
        • RTE initialization and rendering timeline
      • The Cubbles IFrame API
        • The Cubbles IFrame Resizer API
      • The Cubbles mutation based start event API
      • FAQs
        • How to manually resolve dependency conflicts?
        • How to create a component instance dynamically?
        • How to render HTML Markup coming from input slot?
        • How to replace a dependency when declaring a component instance?
        • How to synchronize multiple dataflows between component instances?
        • How to handle the copyValue flag for non serializable instances?
    • Contributor guide
      • CIF processing
  • Developing with the vanilla boilerplate
    • Creating a new project
    • Developing elementaries using the vanilla boilerplate
    • Developing compounds using the vanilla boilerplate
    • Using the vanilla boilerplate scripts
  • Coder devtools - CDT
    • User guide
      • Create Cubbles artifacts
      • Upload a Webpackage
      • Generate a README file
      • Rename an artifact
      • Configure network proxy
      • Validate the manifest.webpackage file
      • Change active webpackage
      • Bulk upload of webpackages
      • Release a webpackage
      • Update the RTE version of a webpackage
      • Prepare a webpackage to be released
      • Update webpackage to the next development version
      • Generate a test environment for a component
      • Testing Cubbles components
      • Validate sources
      • Create a demo webpackage
    • Contributor guide
      • Checklist for releasing a new webpackage.modelVersion
  • Terms and concepts
    • Webpackage
    • Artifacts
    • User roles
    • Base
Powered by GitBook
On this page
  • RTE Bootstrap timeline
  • Event API
  1. Runtime extension - RTE
  2. User guide
  3. The RTE Processing

RTE initialization and rendering timeline

PreviousThe RTE ProcessingNextThe Cubbles IFrame API

Last updated 6 years ago

RTE Bootstrap timeline

Event API

All the events described below are bubbling; thus, they can be caught (listened) on the document Node.

Event

Emitter

Description

crcDepMgrReady

CRC Root Element *

Indicates that all dependencies are resolved, assigned resources are injected into head section and executed. If there are is an asynchronous execution inside these injected resources, they might not be finished or started at all.

crcReady

CRC Root Element*

Fired if CRC has finished working and the afterMainScript.js script was called.

cifInitStart

CRC Root Element*

Fired after CIF has instantiated all Cubbles components on a page and just before all assigned initial slot values are set.

cifInitReady

CRC Root Element*

Fired after all assigned initial slot values are set on each Cubble component instances.

cifReady

CRC Root Element*

cifDomUpdateReady

CRC Root Element*

Replaces the cifReady event when Cubble components are dynamically added to DOM tree after initial CIF processing.

* If not specified explicitly, it is the body node

Fired when all Cubble components are instantiated and the slot initialization is done. The Cubbles component instances are now ready to use (including their ).

Javascript API
RTE Bootstrap timeline