Intro
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,
- lets your browser download the related resources (html, js, css etc.).
Now the RTE / CIF (Component Interaction Framework)
- waits for the ressources to be available,
- creates the component instances (aka "cubbles") and
- initialises each cubble with values provided by the developer.
User Guide
- 2.4 | User Guide
- 2.4 | RTE Integration
- 2.4 | The Cubbles Tag API
- 2.4 | The Cubbles IFrame API
- 2.4 | The Cubbles IFrame Resizer API
- 2.4 | The Cubbles Javascript API
- 2.4 | RTE processing
- 2.4 | The Cubbles Mutation Based Startevent API
- 2.4 | FAQs
- 2.4 | FAQ: How to manually resolve dependency conflicts?
- 2.4 | How to replace a dependency when declaring a component instance?
- 2.4 | How to render HTML Markup coming from input slot?
- 2.4 | How to synchronize multiple data flows between component instances?
- 2.4 | How to create a component instance dynamically?
- 2.4 | How to create nested component instances dynamically within elementary Cubbles components
- 2.4 | Contributors Guide
Recently updated
Open issues in JIRA