GBC 1.00.50 new features and upgrade notes

A summary of new features and changes in functionality introduced with Genero Browser Client (GBC) 1.00.50. Note the changes you may need to make when moving to this version of the GBC.

Important:

This version of GBC is desupported, use a more recent version of the product.

Important:

This page covers only those new features introduced with the Genero Browser Client version specified in the page title. Check prior new features pages if you migrate from an earlier version.

For a detailed list of GBC 1.00.50 changes, please refer to the list of fixes on our issue tracker.

Universal Rendering

Customization built on top of GBC 1.00.50 may be used to render applications in Genero 3.21 native clients (GDC, GMA, GMI) thanks to the Universal Rendering.

Window close icon

The Window close icon is now only visible if a close action is present on the window. When a modal window is displayed, there will not be close icon on the top blue chromebar to avoid duplicates.

Widget creation best practices

To create a widget, you have to use widget factory like this:

var button = cls.WidgetFactory.createWidget("Button", opts);

opts is an object which contains some parameters for the widget constructor. One of these option is recommended: opts.appHash which contains the current application id. This option is used by the GBC core to detect memory leaks.

You can also get all the build parameters of a widget by using WidgetBase.getBuildParameters().

The most simple way to build a widget from another widget is to use this syntax:

var button = cls.WidgetFactory.createWidget("Button", this.getBuildParameters());

For further information, see Customizing your application using widgets.

Widget mouse management

GBC now handles all mouse click events and dispatches them to widgets. Simply override WidgetBase.manageMouseClick(domEvent) and this function should be automatically called when a click is done on the widget.

manageMouseClick: function(domEvent) {
  // Add code to execute when mouse click is handled
  // domEvent parameter is the DOM js event
  return true; // if return true, event is bubbled to parent DOM widget
}

For further information, see Customizing your application using widgets.