Customizing the IDE

A GEB OEM license grants the buyer the right to distribute a customized IDE without usage limitations. The only restriction is: a single license corresponds to a single customized IDE, with its own set of devices and libraries.

OEM data: logo, name and other settings

Each OEM IDE must have some "OEM data" information. There are two alternatives:

Two files `oem.properties` and `oemlogo.png` inside a `oemdata` dir. Say (assuming the IDE in installed in C:\geb) :
```
C:\geb\oemdata\oemlogo.png
C:\geb\oemdata\oem.properties
```
A single `oemdata.zip` file, which includes the above two files in a single Zip-compressed file
```
C:\geb\oemdata.zip  : contains oemlogo.png + oem.properties
```

The logo (oemlogo.png) is a PNG file which is displayed in several parts of the IDE, mainly in the About dialog.

The properties file (oem.properties) specifies the following, in Java properties file format, using UTF-8 charset encoding.

A sample oem.properties file:

name=MYCO LLC
oemid=F453
idename=MYCO 61131-3 IDE
gebversion=3.2.13
checkurl=NONE
updateurl=NONE
signature=MNiYslBR9TJ4PBGvn7HLKXtQm7TuP-bN_xkcv6gF8...

An explanation of each property is given below.

name OEM Company name
oemid OEM private identification, as assigned by GEB Automation when purchasing the license. (Note: an oemid is tied to one OEM license; if the same company purchases more than one OEM license, the name will be typically the same but each IDE will have its own oemid identifier).
idenameName of the IDE, to be displayed to the user.
gebversion Target version of the IDE
checkurl,updateurl These URLs are used for online check of new versions and/or online updates. The special values GEB and NONE can be used; the first means the default urls used by GEB Automation. NONE means that the online checks/updates are not available. Side effect: when checks/updates are enabled, the IDE should be started from a script (geb.bat or geb.sh), otherwise a warning will be shown. If they are disabled (NONE) no warning will appear.
signature Digital signature generated by GEB Automation. Each time one of the above fields change (including the version) an new signature is required.

Splash image

To replace the splash image that appears on startup, make your own image (about 500 x 250 pixels) and save it as 24bits BMP format in ide\configuration\splash.bmp

Then replace the (default) line in ide\configuration\config.ini

 osgi.splashPath=platform:/base/plugins/com.gebautomation.ide

 osgi.splashPath=platform:/base/configuration

 osgi.splashPath=platform:/base/configuration,platform:/base/plugins/com.gebautomation.ide

For the change to take effect, it might be necessary to delete the cached file inside the dir ide\configuration\org.eclipse.equinox.launcher\com.gebautomation.ide_<VERSION>\

Customize IDE colors

IDE colors can be customized by the OEM provider by two alternative methods:

1. From the IDE. In the Window->Preferences dialog, select General->Appearance->Colors There you can set colors for the different parts of the IDE, by selecting a component a pressing the "Edit" button. The suggested items to change are those under the "View and Editor Folders".

When you are done, exit the IDE, and look for the file "org.eclipse.ui.workbench.prefs" in the folder c:\geb\workspace\.metadata_x\.plugins\org.eclipse.core.runtime\.settings\

This is the file that must be copied as explained below

2. Alternatively, you directly edit the file "org.eclipse.ui.workbench.prefs" The colors are expressed as RGB tuples (0-255). Each relevant lines specifies a customized colour for a UI component, for example

org.eclipse.ui.workbench.ACTIVE_TAB_TEXT_COLOR=0,64,0
org.eclipse.ui.workbench.ACTIVE_NOFOCUS_TAB_BG_START=192,192,192
org.eclipse.ui.workbench.ACTIVE_NOFOCUS_TAB_BG_END=64,128,128

In this example, the first line specifies the colour (dark green) for the active view and title text (foreground). The second and third specify the background for the "active but without focus" tabs. The START/END suffixes denote the primary/secondary colours for a gradient fill.

The IDE must be restarted for this changes to take effect.