"Orange box" implementation issues
The "orange box" is a shorthand for the skeleton bridge infrastructure and utilities as shown here
Term infrastructure and utilities refers to the collection of services used to:
Image 1
Since all these UI elements need to available before creating any control wrappers (like wrappers for the KendoUI controls that are then subsequently used in the KendoUI catalog app, we need to create the initial set of controls as Aurelia UI components. We will consider them to be "Aurelia native controls" for the purpose of the skeleton bridge. Because of the existing precedent, where Aurelia Navigation Skeleton already uses Bootstrap navbar I propose that we use Bootstrap UI wrapped controls.
As the image 1 suggests we need:
- Main menu bar: http://getbootstrap.com/components/#navbar)**
- Auxiliary menu bars: http://getbootstrap.com/components/#btn-dropdowns)**
- Button: http://getbootstrap.com/javascript/#buttons
- Tabs: http://getbootstrap.com/javascript/#tabs
- Collapse (accordion): http://getbootstrap.com/javascript/#collapse-example-accordion
These should be implemented as a built-in part of the skeleton bridge to avoid nesting of bridges.
Image 2
The online help system is a reference to the content of this folder used in KendoUI bridge
In this task we need to remove the dependency of the doc.js class on KendoUI panelbar - by replacing it with the accordeon discussed in "catalog application" basic user interface, above.
3. Utilize plugin builder
At the moment, KendoUI bridge and Materialize bridges use the plugin builder as shown here - in the form that is not sufficiently "general" to be a part of this skeleton bridge component.
I am also not aware of Jeroen's specific plans for the "real implementation" of the plugin builder, its configurability and interaction with the wrappers - leaving this part of the article to Jeroen