GBC 6.00.03 new features and upgrade notes
A summary of new features and changes in functionality introduced with Genero Browser Client (GBC) 6.00.03. Note the changes you may need to make when moving to this version of the GBC.
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 6.00.03 changes, please refer to the list of fixes on our issue tracker.
Previous new features page: GBC 6.00.02 new features and upgrade notes.
Vite-based build process
The Genero Browser Client is transitioning from its legacy gbc build system to a vite-based build process, with the goal of improving performance, maintainability, and alignment with modern web tooling.
Starting with GBC 6.00.03, the same gbc build commands now delegate the heavy lifting to vite when you pass --vite as a parameter. The overall workflow and command-line interface (CLI) remain familiar, but the underlying engine is vite.
This is a first step in a longer-term transition. Because GBC still relies on JSFace and modulum internally, the full performance benefits that vite can offer are not yet realized. As those legacy dependencies are progressively removed in future releases, the vite-based build will be able to deliver increasingly optimized output.
Vite will become the default build method in a future release; at that time, the
--vite flag will no longer be needed. You are encouraged to try it now to
familiarize yourself with the new tooling and identify any issues early.
| Legacy CLI | Vite CLI |
|---|---|
gbc build |
gbc build --vite |
gbc build --customization <customization/path> |
gbc build --customization <customization/path>
--vite |
To learn more about vite, visit https://vite.dev.
To see where these commands are used, go to Set up your GBC build environment or Create a customization project.
Enabling AI in the GBC
AI features are disabled by default; they must be enabled using the theme variable gbc-ai-enabled.
To activate AI features, set the theme variable to true. To set theme variables,
you must create or edit a GBC customization project.
Configuring AI
Connect to your AI provider in the AI section of the GBC Settings dialog.

For more information on completing the AI section of the Settings dialog, refer to GBC Settings.
AI configuration on the end-user side is subject to change. This setting allows you to evaluate GBC AI features today; however, Four Js is working to integrate AI such that configuration will not be needed on the end-user side.
Add an AI provider
By default, a GBC project includes six default AI providers; GBC allows adding new AI providers through customization.
You implement a custom provider with a JavaScript module that extends the base class:
AIProviderBase. Once you register the provider, it becomes available in the
AI section of the Settings dialog.
The GBC project package includes a customizaton named custo_ai that serves as an example of how to add a custom provider.
AI Rewrite for TextEdit widgets
GBC integrates AI capabilities to assist users when writing content. The AI Rewrite feature is available for TextEdit components with a toolbar.

In the toolbar:
- A magic wand icon triggers the rewrite action.
- A dropdown chevron provides additional actions.
Available actions include:
- Rewrite text
- Make tone more professional
- Make tone more casual
- Make the text longer
- Make the text shorter
If the user selects a portion of the text, only the selected part will be rewritten; if no text is selected, the rewrite applies to the entire content.
When a rewrite is triggered:
- A floating banner appears indicating that the context is being analyzed. The AI collects relevant information from the current form context, including values from other widgets.
- A second banner then appears and displays the rewritten version of the text in an editable field.

The user can then use the icons in the toolbar to:
- Apply — Replace the original text with the improved version
- Refresh — Generate a new rewrite
- Cancel — Close the rewrite interface
The GBC project package includes the sample textEditAIRewriter, located in the
directory tests\genero_samples\public. This sample shows a form with a
TextEdit widget set up to use the AI Rewrite feature, once AI is enabled for the
GBC. For more information, go to Enabling AI in the GBC.
AI Rewrite uses values from the current form as context. To improve the quality of the generated
results, provide additional details about each field in the form design file with the
COMMENT or TITLE attributes (if using a text-based
.per file) or properties (if using a graphical form design
.4fd file). These details help the AI better understand what each field
represents and what kind of data it contains.
...
ATTRIBUTES
EDIT order_number = FORMONLY.order_number,
DEFAULT = "123456789",
COMMENT = "Unique number that identifies the order";
EDIT customer = FORMONLY.customer,
DEFAULT = "YesCompany",
COMMENT = "Name of the customer who placed the order";
TEXTEDIT textedit_ai = FORMONLY.textedit_ai, STYLE="textFormat_html", STRETCH=both;
END
...
For more information on the COMMENT or TITLE attributes, refer
to the Genero Business Development Language User Guide.
AI Core theme variables
The AI core theme variables apply to all AI providers.
| Theme variable | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
Defines the base prompt used for AI rewriting. Line breaks in prompts are inserted using:
|
|||||||||||
|
Defines how the prompt is structured before being sent to the AI. Available placeholders include:
|
|||||||||||
|
These variables define the prompt fragments used to control the tone. These fragments are used when the user selects the rewrite actions of:
|
|||||||||||
|
These variables define the prompt fragments to control how the AI adjusts text length. These fragments are used when the user selects the rewrite actions of:
|
AI Provider-Specific Overrides theme variables
Each AI provider can override the default rewrite prompts and templates.
| AI provider | Provider-specific override theme variables |
|---|---|
|
Anthropic |
|
|
Chrome Rewriter |
|
|
Google (Gemini) |
|
|
Mistral |
|
|
Ollama |
|
|
OpenAI |
AI User Interface (UI) Color theme variables
| Theme variable | Description |
|---|---|
ui-ai-color |
Identifies AI-related elements in the user interface. The interface uses this color for:
|
FloatingBanner theme variable
The FloatingBanner is not a Genero BDL widget. It is an internal GBC component used by features such as AI Rewrite and Offline Mode.
| Theme variable | Description |
|---|---|
gbc-FloatingBannerWidget-shadow-color |
Controls the shadow color of the FloatingBanner component. |
AI Rewrite Presentation Style
Use the aiWritingAssistant presentation style to enable or disable the AI
Rewrite feature for a specific TextEdit field.
- When set to
yes, the AI Rewrite feature is enabled for the TextEdit field where this presentation style attribute is applied, but only if the GBC has the theme variablegbc-ai-enabledset totrue. - When set to
no, the AI Rewrite feature is disabled for the TextEdit field where this presentation style attribute is applied.
For more information on the aiWritingAssistant presentation style and how to use
it, refer to the Genero Business Development Language User Guide.
ComboBox simple construct presentation style
<StyleAttribute name="customWidget" value="comboBoxSimpleConstruct"/>For more information, go to ComboBox style attributes in the Genero Business Development Language User Guide.
TabbedContainer applications display in ChromeBar
While tabbedContainer applications have been deprecated since Genero BDL 4.00, the use of
tabbedContainer=yes continued to embed each application in a tabbed container with
several specific behaviors.
tabbedContainer=yes is treated like
applicationListPosition="top". All applications display in the ChromeBar as
closable tabs; the tabs will shrink depending on the available size of the ChromeBar. This aligns
the display of and access to tabbedContainer applications with that of other applications, which
means the following previous tabbedContainer-specific behaviors no longer apply: - The parent application menu is still present but is no longer permanently visible, as other applications are not contained inside the parent application container.
- The SideBarDrawer is no longer automatically docked. To restore this behavior, set the theme
variable
gbc-MainContainerWidget-left-dock="sidebardrawer". - The app section of the SideBarDrawer is now collapsed rather than completely removed. This can
be controlled with the theme variable
gbc-SideBarDrawer-AppsSection-show. - Tabs now display the application title instead of the window title.
- Closing the parent application no longer closes all child applications.
tabbedContainer=yes– just likeapplicationListPosition="top"– is not supported by mobile applications.
tabbedContainer presentation style and how to use
it, refer to the Genero Business Development Language User Guide.Accessibility improvements for button-related widgets
Four Js is working on better accessibility standard compliance which may impact customization migrations. Specifically with GBC 6.00.03, accessibility improvements have been completed with regard to button-related widgets.
To complete these improvements, some widget templates and CSS have been updated; the changes, however, are minor.