...
About this Manual
...
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.
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.
| 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. |
Who should read this manual
This manual is a must read if you wish to develop your own custom library of component(s) using the Canvas core layer or override any existing component. By default, Canvas does not force an implementation to consume the default components that have been packaged. If you are a lead or an architect, you might also want to know about the container level control on every component by which you can enable your web designing team to do certain implementation specific designing. In short, the core layer comes with its own advantages of DOM management and event handling capabilities, which are dependent on the library layer at every level.
How is this manual organized?
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 3 summarizes the Canvas core layer and provides a pictorial representation of the Canvas core layer process flow.
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
| Page Tree | ||
|---|---|---|
|