How to add a canvas field to a Form or Grid
Contents
Introduction
A canvas field allows you to add any visual component to a form or a row in a grid. This concept can be used to add a calculated field to a form and grid. Visual components which can be added are for example buttons, links and (computed) labels.
In this howto we will be adding a button and a calculated field to the form and to every row in the grid. The howto will illustrate how information from the record and form can be used to get dynamic information from the Form/Grid.
The implementation of canvas fields requires javascript development experience. See the following concept pages for background information on javascript development:
It also makes sense to study the following page: Openbravo_3_Architecture.
Note: this functionality is available in Openbravo 3.0 from MP6 and later.
Example Module
This howto is supported by an example module which shows examples of the code shown and discussed.
The code of the example module can be downloaded from this mercurial repository: https://code.openbravo.com/erp/mods/org.openbravo.client.application.examples/
The example module is available through the Central Repository (See 'Client Application Examples'), for more information see the Examples Client Application project page.
Main development steps for creating a new canvas field
The development consists of 2 steps:
- implement the canvas itself, normally this is done in javascript.
- specify the canvas javascript class in the field definition of the tab/window
Implementing your canvas in javascript
The first step is to implement your canvas class in javascript. This is done in 2 steps:
- Create a javascript file with your javascript class and place it in the correct directory, the convention is to place js files in the following directory in your module: web/[module.java.package]/js
- Register the javascript file (and other static resources such as css files) in Openbravo using a ComponentProvider
The example module implements a button and a calculated field in the example-canvas-field.js file.
The first example in the file implements a button which shows the identifier of the current record: <source lang="javascript">isc.defineClass('OBEXAPP_SalesOrderActionButton', isc.OBGridFormButton);
isc.OBEXAPP_SalesOrderActionButton.addProperties({
noTitle: true,
title: OB.I18N.getLabel('OBUISC_Identifier'),
click: function() {
var info = ;
if (this.record) {
info = this.record._identifier;
} else if (this.canvasItem) {
info = this.canvasItem.form.getValue(OB.Constants.IDENTIFIER);
}
isc.say(info);
}
}); </source>
The second example shows a calculated field which divides 2 values from the current record and displays the result in a formatted way. It also illustrates several methods which are called when the context/environment changes (for example when a value on the form changes): <source lang="javascript">isc.defineClass('OBEXAPP_SalesOrderCalculated', isc.Label);
isc.OBEXAPP_SalesOrderCalculated.addProperties({
height: 1,
width: 1,
overflow: 'visible',
contents: ,
initWidget: function() {
if (this.canvasItem) {
this.computeContents(this.canvasItem.form.getValue('grandTotalAmount'), this.canvasItem.form.getValue('summedLineAmount'));
}
this.Super('initWidget', arguments);
},
// is called when the form gets redrawn
redrawingItem: function() {
this.computeContents(this.canvasItem.form.getValue('grandTotalAmount'), this.canvasItem.form.getValue('summedLineAmount'));
},
// is called when a field on the form changes its value
onItemChanged: function() {
this.computeContents(this.canvasItem.form.getValue('grandTotalAmount'), this.canvasItem.form.getValue('summedLineAmount'));
},
// is called in grid-display mode when the canvas is created/used
// for a record
setRecord: function(record) {
this.computeContents(record.grandTotalAmount, record.summedLineAmount);
},
computeContents: function(val1, val2) {
var num;
if (!val2) {
this.setContents();
} else {
num = OB.Utilities.Number.JSToOBMasked(val1/val2,
OB.Format.defaultNumericMask,
OB.Format.defaultDecimalSymbol,
OB.Format.defaultGroupingSymbol,
OB.Format.defaultGroupingSize);
this.setContents(num);
}
}
}); </source>
The javascript file is registered in the example modules' ComponentProvider like this: <source lang="java"> @Override
public List<ComponentResource> getGlobalComponentResources() {
final List<ComponentResource> globalResources = new ArrayList<ComponentResource>();
globalResources.add(createStaticResource(
"web/org.openbravo.client.application.examples/js/example-canvas-field.js", false));
.....
</source>
Defining the canvas in the Tab-Field (ADField)
The next step is to create a new field in the tab, and set its client class field:
Since 3.0MP20 it is also possible to add in-line properties in the "Clientclass" field, for example, 'OBEXAPP_SalesOrderActionButton {"title": "My Action Button"}'
The result
The result is shown in both the grid and the form:
Javascript events passed to the canvas
When implementing your canvas you should take into account that the canvas is used in 3 different situations:
- when displaying a row in the grid
- when editing a row in the grid
- in form view, when editing a record
The last 2 cases are similar.
In grid-display mode the following applies:
- in grid mode the following properties are set on the canvas:
- grid: the grid object
- rowNum: the row number/record index for which the canvas is used
- record: the record for which the canvas is used
- colNum: the column in which the canvas is shown
- field: (since 3.0MP20) the field where the canvas is used
- a canvas can be created and pooled, so over time it is created once and re-used when records are scrolled into view. When a canvas is used for a record then the setRecord method on it is called (if the canvas has this method).
In form-edit or grid-edit mode the following applies:
- the canvasItem property will be set pointing to the form item the canvasItem can be used to get to the form itself and to the grid (if editing in the grid):
- this.canvasItem.form: the form instance
- this.canvasItem.form.grid: in case of grid editing
- if the canvas has a property noTitle with the value true then in form mode no title/label is displayed
- Form changes: the canvas can capture form/value change events by implementing 2 methods (both without arguments):
- onItemChanged: is called when a value on the form changes
- redrawingItem: is called just before the form is redrawn
Adding server side actions
The button implementation can easily be extended with a server side action. Openbravo supports the action handler concept for this purpose.
