App Shell
Last updated
Last updated
A view exposed from your app should follow the principle. It needs to import the dependencies and be able to render itself. It must not assume how and where it is inserted in the main document and must not expect the presence of any APIs other than <starcounter-include>
and .
The view is inserted in the main document by another view or, if it is at the root of the view-model, by the Starcounter app shell.
The Starcounter app shell is a minimalist, configurable HTML document that imports the prerequisites for all blendable web apps:
a polyfill for the browsers that do not have a native implementation of the Web Components specs
Palindrom JS library for communication with the server
the <starcounter-include>
custom element
Bootstrap, a CSS framework
On page load, the app shell establishes the Palindrom session with the server, obtains the JSON view-model tree, inserts the root view using <starcounter-include>
and connects the root view to the view-model.
The default content of the app shell is tied to the StarcounterClientFiles version that is bundled with your Starcounter installation. The current version can be previewed in the . You can upgrade or downgrade the app shell by installing another version of StarcounterClientFiles from the App Warehouse.
The app shell is invoked automatically for any Json
with a Html
property that is returned from your app. The only provision is that your app needs to register the following middleware:
It is strongly advised to use the default, unmodified app shell. The default app shell is the lowest common denominator for all apps. If you change it, you might introduce side effects that make your app incompatible with other vendor's apps.
The page explains the APIs presented above. In short, the HtmlFromJsonProvider
middleware fetches the view associated with a view-model, and PartialToStandaloneHtmlProvider
wraps the view in the app shell.
If you need to modify the app shell, follow the instructions on the page.