Skip to end of metadata
Go to start of metadata

In various places the Servoy brand is exposed to users of both Smart and Web Clients. To customize the user experience, these exposures to the Servoy brand can be overridden to expose a custom brand.

There are several locations that require updating to fully customize the user experience:

  1. Branding Settings
  2. Default webpages
  3. Library signing

Branding settings

The Servoy Admin page exposes several Branding settings on it's main page. By enabling Branding support (setting the "servoy.branding" setting to true) and providing custom values for the other properties, the first part of the user experience can be customized.

Setting

What it controls

Where

servoy.branding

Controls whether or not all the other Branding settings are applied or not

N/A

servoy.branding.webstart.splash

Controls the splash screen shown by WebStart when launching a Smart Client

Smart Client

servoy.branding.webstart.loadinglogo

Controls the image used inside WebStart UI's

Smart Client

servoy.branding.webstart.vendor

Controls the Vendor name displayed in WebStart

Smart Client

servoy.branding.webstart.shortcuttitle

Controls the label text for Desktop Shortcuts

Smart Client

servoy.branding.windowtitle

Controls the text in the TitleBar and/or browser tab

Smart & Web Client

servoy.branding.windowicon

Controls the Icon used in the TitleBar and/or browser tab

Smart & Web Client

servoy.branding.loadingimage

Controls the image shown in the Smart Client at startup, before a Solution is loaded

Smart Client

(warning) Branding settings only have effect on the Servoy Application Server, not for Debug Clients in Servoy Developer

Default webpages

Servoy contains a number of webpages for starting client and exception handling. All these pages can be customized.

Page

Customization location

Used for

Comments

index.html

{servoyInstall}\application_server\server\webapps\ROOT\index.html

Starting Smart Clients

This page is also the default webpage shown when accessing just the serverUrl

SelectSolution.html

{servoyInstall}\application_server\server\webapps\ROOT\servoy-webclient\templates\default\SelectSolution.html

Starting Web Clients

The list can be empty if solution browsing is disabled

SignIn.html

{servoyInstall}\application_server\server\webapps\ROOT\servoy-webclient\templates\default\SignIn.html

Default Web Client login page

Solutions can override page by implementing a Login solution for authentication

ServoyExpiredPage.html

{servoyInstall}\application_server\server\webapps\ROOT\servoy-webclient\templates\default\ServoyExpiredPage.html

Page shown when a Web Client session expires

 

ServoyServerToBusyPage.html

{servoyInstall}\application_server\server\webapps\ROOT\servoy-webclient\templates\default\ServoyServerToBusyPage.html

Page shown when trying to start a new Web Client and there are no licenses left

 

UnsupportedBrowserPage.html

{servoyInstall}\application_server\server\webapps\ROOT\servoy-webclient\templates\default\UnsupportedBrowserPage.html

Page shown when a new Web Client is being started in an unsupported browser

The only unsupported browser currently is Internet Explorer <6 IF anchoring is enabled. See "servoy.webclient.enableAnchors" for more info

(warning)  All the pages of which the Customization location starts with "{servoyInstall}\application_server\server\webapps\ROOT\servoy-webclient\templates\default", there is no file stored by default. These pages are virtual, until they are manually stored in their Customization location. The virtual version can be accessed through the url "_{serverUrl}/servoy-webclient/templates/default/": the source of the relevant page needs to be saved to file in the Customization location, using the page name as filename for it to be used instead of the virtual version.

Library signing

When using the Smart Client for the first time, the user will be presented with a Security dialog of Java WebStart, asking the user to trust the vendor of the libraries of which the application consists.

All libraries that come with Servoy are signed by Servoy, thus the user will be presented with the Security dialog and asked to trust the vendor Servoy.

It is possible to resign all the libraries using a Signed Certificate issued with a differetn vendor name. For more information on resigning the libraries, see SignTester tool on ServoyForge.

  • No labels