With the help of the Object Nationalizer you can change or adapt all visual objects without changes to the source code. This means you can rename labels, group boxes, hide fields, enlarge fields, reposition fields or columns in tables or hide menus. In other words you can create different variants of GCRS or GHS which cover one existing functionality with different user interfaces.

In which situation would I use this possibility ?

You could use this possibility for instance when you want to adapt the layout of the screens for the optimal use of different end user devices. You could also use it for specific language adaptations. If you want to roll out a certain functionality of GCRS which is controlled by the user interface and behaves like hard coded and not dynamically administrated by database parameters.

Will changes which I do with the Object Nationalizer change the Source could of GCRS ?

No they will not. It will change existing visual objects. Will I loose my changes when I use and new version or an update of GCRS from Galilei Software. When you change the user interface you would store all changes in a separate text file . When a new update or upgrade arrives you just apply this text file with the Object Nationalizer to the newer version. The new version will then carry you individualized user interface.

Can I use the Object Nationalizer to create versions in other languages ?

Yes, this was one of the main purposes wy the Object Nationalizer was developed. In addition to this Galilei has developed a so called Visual Object Source Parser (VOSP) which can extract all string objects an store them into an Excel-Table. A human translator or an automatic translation program could create the translations line by line in an extra column and the return it to the Visual Object Source Parser. VOSP would then replace all language elements in the visual objects resource file. By applying this resource file to the executable, you would create a new language version.