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

Runtime extension - RTE

PreviousCompound slot initializationNextUser guide

Last updated 6 years ago

The RTE (RunTime Extension) works within the clients webbrowser. Just integrate the RTE into a web page with 2 simple script tags and you are ready to use Cubbles components.

The RTE/CRC (Client Runtime Container)

  • identifies the Cubbles Components used on the webpage,

  • resolves the resources needed to instantiate the Cubbles Components,

  • enable your browser to download the related resources (html, js, css etc.).

Now the RTE/CIF (Component Interaction Framework)

  • waits for the resources to be available

  • creates the component instances (aka. "cubbles") and

  • initialises each cubble with values provided by the developer.

Do you want to use Cubbles on your website? Follow the .

Do you want to contribute to Cubbles Open Source Project or get to know the Cubbles technology in detail? Follow the .

User Guide
Contributor Guide