When you package and deploy a customized version of the Genero Browser Client, a suffix is appended to the version number. This suffix lets users know that the version of the GBC being used is a customized version. By default, the suffix is "c
",and it appears in:
- the version number displayed in the Info dialog of the GBC interface.
- the name of the customization zip file.
This procedure shows you how to change the suffix from the default (c
) to a value of your own choosing.
Before you begin
- You have a customization directory,
gbc-project-dir
/customization/
customization-project-dir
with aconfig.json
file. If the file does not exist, create it.
TIP: Use a copy of the
config.json
file provided in the sample customization folder as a starting point.
Update the config.json file
Edit gbc-project-dir
/customization/
customization-project-dir
/config.json
to define customizationSuffix
in the root object of the config.json
file of your customization, as in this example:
{
"customizationSuffix" : "mySuffix",
"themes": [{
"name": "default",
"title": "Default",
"uses": ["platform/desktop", "common"]
},
... additional themes would be listed here ...
]
}
Effect on version information displayed
With customizationSuffix
set to mySuffix
, the version information displayed now displays:
Version 1.00.
xx
.mySuffix
, wherexx
represents the build number.
Effect on GBC customization package file
With customizationSuffix
set to mySuffix
, the zip package name (created with the gbc build
option --create-zip
) now includes the suffix. The zip package file name is:
fjs-gbc-1.00.
xx
.mySuffix-build
yyyyyyyyyyy
-customization_sample.zip
, wherexx
represents the build number andyyyyyyyyyyy
represents the build timestamp.