Within the Spark Table and Service Data Table controls there is a configuration option to manipulate how the columns in the table are rendered on the page. This article will discuss the differences between the different rendering types and when to use each. You can also view the Spark Showcase process app or the Table knowledge base article here to learn more about the Table control.
Different Rendering Types
Coach View:
The coach view render type is the most data-intensive of all the options, meaning there are performance considerations when rendering columns. The coach view option allows controls within the column to be treated as coach views with the ability to perform JavaScript logic. Rendering as a coach view is necessary for any type of control that will use Spark events or be used in the evaluation of JavaScript.
Within the onClick() event, the modal section is made visible by clicking the button. This is an example of when a developer would want to render this column as a coach view.
Seamless Coach View
The seamless coach view render type removes the border of the controls nested within a table during rendering. Example controls where this could be applied would be typical form input controls, such as: the Integer control, Date Picker, and Decimal. Other than the difference in appearance this rendering type is treated the same as a coach view.
The image below shows the difference between rendering as a seamless coach view and rendering as a coach view.
Simple HTML
The simple HTML render type is the least data intensive rendering type of all the options. The simple HTML renders the content using pure HTML. This type should only be chosen if the fields in the table have no JavaScript logic executed. If JavaScript is used within the field (i.e. in a control's event) when set to render as simple HTML, the control will not render on the page.
Custom
The custom render type is the option a developer would use to specify what a field would look like. When editing the information in the Columns Configuration tab, there is an input box labeled "Options." Within here a developer has optional formatting to apply to already created objects. Using "Options" only works when rendering as simple HTML or as a Custom column.
The image below applies the following column options: 'decimalPlaces': 2, 'decimalSeparator': '.', 'thousandsSeparator': ',', 'prefix':'$'
- Author: Elliot Pytosky
- Date Created: November 9, 2015
- Date Modified: November 9, 2015
Comments