GBC 4.01
Customization
How customization works
Planning for the customization Getting the customization to the user
Set up your GBC build environment Create a customization project Rebuild the GBC
Create a runtime package Deploy on GAS Deploy on JGAS Change the version customization suffix
Manage themes
Add a theme part Add a theme Modify a theme Delete a theme
Replace an image
Change the favicon Change background image for empty tabbed container
Use theme variables
Display or hide the sidebar Customize the chromebar Change checkbox icons Display the Genero context menu Change relog prompt
Use style sheets
Center progress indicator icon Center file loading icon
Use widgets
Add header image Add header image using style class Add header text Add footer text Change file loading icon Redirect application end Extend the MainContainerWidget
Internationalize your app
Add localized text Configure right-to-left languages Customize translation text Default encoding
Migrating customizations
Getting the customization to the user

After you modify a customization and its themes, you package your customization and deploy it to the Genero Application Server (GAS). You can deploy many customizations to the GAS, but only one can be marked as the default customization. Unless otherwise specified, a user receives the default customization.

You can use the URL to specify a different customization.

Within the selected customization, a default theme is used unless:

  • The user has previously accessed the application and selected a different theme. The last selected theme for the user is chosen.
  • The theme is specified specifically in the URL.
  • The theme is set by a frontcall from the application.

When the application is running, the theme can be changed, but the customization cannot. To use a different customization, restart the application with the new customization selected.