There are 4 main ways that developers / users 'interact' with the code in the Adaptable Blotter:
Setting up the Adaptable Blotter through configuring Blotter Options which are passed in to the Adaptable Blotter implementation
Pre-populating the Adaptable Blotter with the objects it requires at startup with all the objects it requires through writing Predefined Configuration
Accessing all the functionality and state in the Adaptable Blotter through code (at runtime) via the Adaptable Blotter API.
There are 2 ways to instantiate a new Adaptable Blotter:
You use the Blotter Options to set up the Adaptabble Blotter at design time so that it fits your requirements. There are 2 mandatory properties (primaryKey and vendorGrid) and a host of optional ones (including Predefined Config - see below). Where a property is not provided, the Adaptable Blotter provides a default. The code documentation lists all the available properties and their default values.
You can provide the Adaptable Blotter at start-up with Predefined Configuration which ensures that when the Blotter first loads it contains all the objects that users need. This includes entitlements.
The Adaptable Blotter API provides full safe, run-time access - through code - to all the functionality and state of the Adaptable Blotter. This allows you to create, save and delete Adaptable Blotter objects in your our screens bypassing the Blotter's UI, or to access the Store in a safe non-mutable manner.
You can find further information about the Adaptable Blotter at these sites:
Generated using TypeDoc