Introduction About Canvas Core Layer

Core 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.

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, TBS and jQuery Mobile for the Desktop Channel and the Mobile/Tablet Channel respectively.

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.

Core Layer Framework has managers at every configurable level, which consume library components registered in a Core Layer Component registry against certain meta data.

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