...
Introduction About Canvas Core Layer
Core Layer is the abstract JavaScript Layer that acts as the base of CORA. It consists of client-side registries and classes in the form of managers, which are responsible for initializing and managing any component being built in the corresponding implementation. Any Canvas framework implementation is expected to be created as per the specifications highlighted in this document.Anchor
This document layer revolves around the Omni-channel concept, which is the capability of an application to manage itself on all and every channel(s). This means, the business functionality developers are able to write and configure their functionality only once without having to worry about the device or channel on which the transaction is going to be performed. Since rendition
Rendition across channels is a basic expectation from a web application of today's standard, the Canvas Core helps in achieving this by drawing a boundary between the functionality and the UI. While application developers register their functionality against a standard set of Canvas defined events, the core layer takes care of providing the appropriate meta data to the library, trigger rendition of the component, and bind these Canvas defined listeners to the UI events exposed by the library.
Hence, there can be any number of libraries depending on the bandwidth of the application, but all of these must have a meaningful mapping against the appropriate channel.
Canvas by default implements two sets of libraries, Ext-JS TBS and jQuery Mobile for the Desktop Channel and the Mobile/Tablet Channel respectively. NOTE:
| Info |
|---|
While the core layer does not place a restriction on any library layer on handling the meta data and the rendition structure, there are a few responsibilities assigned to every library that ought to be fulfilled |
...
. |
...
Section 1 provides a quick overview on how the Core Layer Framework is organized and what are the key aspects of the core layer.
Section 2 provides a complete listing of all the library layers and about registering and managing the meta data for component creation.
Section 3 summarizes the Canvas core layer and provides a pictorial representation of the Canvas core layer process flow.
The following sections represent CT application's client-side architecture on a high level and the meta data mapping of components for the same.
View the following Pages
| Page Tree | ||
|---|---|---|
|