PROVISIO DevBlog

Using the External Script Option of SiteKiosk to Automate Processes

SiteKiosk allows you to run an external script, that you can use to automate processes within SiteKiosk. The external script can contain the SiteKiosk Object Model as well as Wsript. That enables you to script a broad spectrum of tasks.

The example we want to build, will demonstrate an automated Gmail login, that will work with the IE and Chrome browser engines of SiteKiosk.

Our example code looks like this:

//Helper variable to prevent multiple SendKeys at once
var currently_sending_keys = false;

//Initialization of the WScript Shell object used for sending keys
var objShell = new ActiveXObject("WScript.Shell");

//OnMessage event fired by the browser used to start looking for the login page
SiteKiosk.Logfile.OnMessage = OnMessage;

//Handling the OnMessage event
function OnMessage(seq, time, utcoff, awtype, awlevel, facility, text){  
   //Check the navigation to identify the login page and whether the script is already sending keys
   if((text === "Navigation: http://www.gmail.com/" || text === "Navigation: http://gmail.com/") && !currently_sending_keys){
	   //Start sending keys so set the helper variable to true
	   currently_sending_keys = true;
	   //Wait a short period of time to give the page time to load and then send the user name
	   SiteKiosk.Scheduler.AddDelayedEvent(1500, SendTheUsername);
   }
}

//Send the user name
function SendTheUsername(eventID){
	objShell.SendKeys("username@gmail.com");
	objShell.SendKeys("{enter}");
	//Wait a short period of time to give the page time to the password part and then send the password
	SiteKiosk.Scheduler.AddDelayedEvent(1500, SendThePassword);
}

//Send the password
function SendThePassword(eventID){
	objShell.SendKeys("password");
	objShell.SendKeys("{enter}");
	//We are done sending keys so set the helper variable to false
	currently_sending_keys = false;
}

Let us have a closer look at some parts of the script.

...
//Handling the OnMessage event
function OnMessage(seq, time, utcoff, awtype, awlevel, facility, text){  
   //Check the navigation to identify the login page and whether the script is already sending keys
   if((text === "Navigation: http://www.gmail.com/" || text === "Navigation: http://gmail.com/") && !currently_sending_keys){
...

The script uses the OnMessage event of the SiteKiosk Object Model to track navigations. If it finds matching navigations to either www.gmail.com or gmail.com and it is currently not sending keys it triggers the automated login.

...
SiteKiosk.Scheduler.AddDelayedEvent(1500, SendTheUsername);
...

Utilizing the AddDelayedEvent method, the script gives the page some time to load. You may need to adjust the time depending on your Internet connection. The function to send the first set of keys for the user name of the Gmail login process is called next.

...
objShell.SendKeys("username@gmail.com");
...

The SendKeys method of the WScript Shell object is used to send key strokes to the browser. First the user name, then the enter key to trigger the password request. Finally the script starts a similar process for the password input mask.

Save the above example code as a javascript file (e.g. automated_gmail_login.js), preferably in the html subfolder of your SiteKiosk installation. Now in the SiteKiosk configuration you have to add the file as an external script. Go to Start Page & Browser and click on the Advanced button. Now you can tick the option that SiteKiosk should execute the script on startup.

Save the configuration and for testing purposes use the Run Once Mode of SiteKiosk. Type in gmail.com or www.gmail.com in the address field of the SiteKiosk browser. The script will attempt to make an automated login with the provided user name and password. Note that the above example script may stop working if the Gmail page layout changes.

Debugging Webpages in the SiteKiosk Windows Chrome Browser

When you are using the SiteKiosk Windows Chrome Browser you can activate the Chrome DevTools to debug web pages in SiteKiosk.

To activate this option, you need to create an empty text file with the file name debug.txt. This file must be placed in the folder ..\SiteKiosk\Chromium\.

When you start SiteKiosk with the Chrome Browser engine after that change, you can click on the browser pane of SiteKiosk and hit the F11 button to open up the Chrome DevTools window.

Remember to delete or rename the debug.txt file after you are done with debugging.

How to Use a Proxy Auto-Config File with SiteKiosk Windows

This time, we will have a look at the different ways to use a proxy auto-config (PAC) file with SiteKiosk.

There are two different methods, depending on the SiteKiosk browser engine you plan to use. No matter which engine you are using, you need to disable the Use proxy server setting of SiteKiosk, otherwise SiteKiosk will use the proxy settings defined in its configuration file instead of those from the PAC file.

When you are using the Internet Explorer engine, SiteKiosk uses the Microsoft IE settings, including a PAC file assigned there. Note that the IE settings are user dependent, so make sure to make these settings within the Internet Explorer of the user you want to run SiteKiosk with.

When you are using the Chrome Browser engine, you need to add your PAC file manually to the configuration of SiteKiosk. Open your SiteKiosk configuration with an editor like notepad. Search for this line:

"showTaskBar": true,

Add these lines right before the showTaskBar line:

"browserEngine": {
       "commandLineArguments": {
           "set": ["proxy-pac-url=urlzuihrerpacdatei"],
           "remove": []
       }
   },

It should look like this:

…
"system": {
    "password": {
      "enabled": false
    },
    "browserEngine": {
       "commandLineArguments": {
           "set": ["proxy-pac-url=UrlToYourPacFile"],
           "remove": []
       }
	},
    "showTaskBar": true,
    "userAgent": {
…

Of course you need to change UrlToYourPacFile to the actual path to your PAC file, e.g. something like file://C:/mylocalpacfile/proxy.pac or http://192.168.99.1:8088/proxy.pac. The configuration part would then look like this:

…
"system": {
    "password": {
      "enabled": false
    },
    "browserEngine": {
       "commandLineArguments": {
           "set": ["proxy-pac-url=file://C:/mylocalpacfile/proxy.pac"],
           "remove": []
       }
    },
    "showTaskBar": true,
    "userAgent": {
…

Please note that the content filter of SiteKiosk does not support using PAC files. Please use the proxy configuration settings of SiteKiosk instead.

Specifically Deny Downloads of Certain File Types

SiteKiosk enables you to only allow the download of certain file types only. You can do this in the configuration editor under Files & Downloads. In rare cases you might need to do the opposite, because you only want to block a handful of file types instead of allowing only a handful of file types.

There are two different ways to achieve this. In both cases you would generally allow downloads in the configuration of SiteKiosk under Files & Downloads. Then, one option is to use the Surfing Area settings. Just create deny entries for each file type you want to block. Use * for the protocol and *.filetypetoblock (e.g. *.zip) for the URL. This only works if the download is a direct link to the file.

The second option applies to the IE engine of SiteKiosk only. You can edit the file ..\SiteKiosk\xml\downloadmanager.xml with a text editor (e.g. Notepad). In the file there is a file extension list that already includes a number of default entries. Just add additional entries for the file types you want to block and set both the values for download and for open to 0. Just like this:

<extension name='zip' download='0' open='0'/>

This tells SiteKiosk to neither download nor open the file. Place the entries at the end of the existing list. You may also edit an existing entry. Make sure to not use the same extension twice, SiteKiosk will only use the first match in the list.

<extension-list>
	<extension name='exe' download='2' open='0'/>
	<extension name='dll' download='2' open='0'/>
	<extension name='htm' download='1' open='2'/>
	<extension name='html' download='1' open='2'/>
	<extension name='pdf' download='2' open='1'/>
	<extension name='jpg' download='2' open='2'/>
	<extension name='gif' download='2' open='2'/>
	<extension name='png' download='2' open='2'/>
	<extension name='txt' download='2' open='2'/>
	<extension name='zip' download='0' open='0'/>
</extension-list>

This will block matching download attempts in SiteKiosk.

Using the Blackboard Information Page on a SiteRemote Server

NOTE: This only applies to customers running their own SiteRemote Server (5.2 and above).

The Blackboard is used by the SiteRemote Server and the SiteKiosk Windows and SiteKiosk Android clients to exchange some internal information. There have been two Developer Blog posts (SiteKiosk Windows, SiteKiosk Android) that have shown how this information can be used on a client with the help of the SiteKiosk Object Model. This post will show how to view all available Blackboard information of a single client machine by adding a page to the teams of a SiteRemote Server. This also enables you to easily search the Blackboard information.

Please be aware that the Blackboard information is limited in its use for purposes other than the internal processes of the SiteRemote server and client communication, under specific project circumstances the option to use it might still be very helpful.

To add the Blackboard page to teams on your SiteRemote Server version 6.1 or higher, go to the Settings page of the SiteRemote Server Administration and check the option Show Blackboard information page per machine and Blackboard machine list filter settings on Team settings page. Save the change. Note that in SiteRemote Server version 6.1 or higher, this will also provide you with the option to create your own machine list blackboard filters. Go to the Administration -> Settings page in a SiteRemote team and look for the Machine List Settings. There you can create machine list filters that search through the blackboard entries of machines.

To add the Blackboard page to teams on your SiteRemote Server version 5.2 to 6.0, you need to edit the file ..\PROVISIO\SiteRemote\Web\Web.sitemap. Open it with an editor and look for these lines:

<siteMapNode url="terminal/logs/view.aspx" title="$(String:683)" accesstype="LogFileTab" displayTreeView="true">
	<siteMapNode url="terminal/logs/createexport.aspx" displayTreeView="true"></siteMapNode>
</siteMapNode>

Add this new line directly after:

<siteMapNode url="terminal/blackboard/blackboard.aspx" title="Blackboard" accesstype="LogFileTab" displayTreeView="true"/>

Afterwards you should get this result:

<siteMapNode url="terminal/logs/view.aspx" title="$(String:683)" accesstype="LogFileTab" displayTreeView="true">
	<siteMapNode url="terminal/logs/createexport.aspx" displayTreeView="true"></siteMapNode>
</siteMapNode>
<siteMapNode url="terminal/blackboard/blackboard.aspx" title="Blackboard" accesstype="LogFileTab" displayTreeView="true"/>

If you now login to a team on your SiteRemote Server and select a machine from the treeview on the left, you will have a new Blackboard tab next to the Logfiles tab of that machine.

The page can slightly differ based on the available Blackboard information of that specific machine.

You can now also use the SiteRemote search feature to search the value fields of the Blackboard. To search through the Blackboard use the bs macro. Let's look at an example, the Blackboard contains the current SiteKiosk configuration of a machine in the key CtS.SiteRemote.Config.Files/d/SiteKiosk. If you now want to find all machines that use the www.your-comp.com URL as the start page, you would simply search vor bs:www.your-comp.com and the result lists all machines with that URL in the configuration.

Starting SiteKiosk Windows Chrome Browser with Multiple Tabs

By default SiteKiosk Chrome starts with the one start page you have configured in the SiteKiosk configuration tool under Start Page & Browser. If you need more than one start page, each using its own tab, you can do this with a little bit of script editing.

The editing needs to be done in the file browserSettings.js. The file is located in the folder C:\Users\Public\SiteKiosk\data\content\local\files\projects\d97aa96b962543fcb39625a3f8e8d8fb\000000000000000000000000\files. Make a backup of the file first and then open it with an editor like Notepad or Notepad++.

Look for the first (applies to SiteKiosk 9.5) occurrence of:

tabControl.newTab();

It is the last line (applies to SiteKiosk 9.5) within the definition of the function exports.initializeTabView.

This line opens the start page configured in your SiteKiosk configuration.

To open additional tabs you need to add the newTab function call as many times as the number of tabs you need. Within those additional function calls, you state the starting URL for a tab.

tabControl.newTab({
	startUrl: "https://www.siteremote.net/"
});

For example, if you want to add two extra tabs to the existing start page, you will need this script code:

tabControl.newTab();
tabControl.newTab({
	startUrl: "https://www.siteremote.net/"
});
tabControl.newTab({
	startUrl: "http://devblog.provisio.com/"
});

Please note a few things you should consider when using this customization. If you allow the new window button (Start Page & Browser -> Chrome Browser -> Customize -> Browser Toolbar -> Show New Window Button), new windows will also open with the added tabs. The active tab when loading SiteKiosk or a new window is the last tab in the list. You should not add more tabs than allowed in the SiteKiosk configuration (Start Page & Browser -> Chrome Browser -> Customize -> Advanced -> Maximum number of browser windows/tabs), the default number is 5.

When starting the above example with SiteKiosk the result will look like this:

Customizing the Digital Signage Player of SiteKiosk Windows

Based on the article "Customize the SiteCaster Player in SiteKiosk" (http://devblog.provisio.com/post/2012/01/17/Control-SiteCaster-Player-in-SiteKiosk.aspx) we will examine another scenario for the customization of the Digital Signage player of SiteKiosk Windows.

The example scenario is from a specific customer project and the requirements are as follows ():
1. Digital signage is running in full screen mode.
2. The screensaver (showing the SiteKiosk Player) is allowed and while the screensaver is active, the campaign stops.
3. When the screensaver is deactivated, the campaign needs to be played from the beginning.

This can be useful when having a video playing in the campaign and you do not want any distraction from what you are showing as the screensaver. The requirements can be realized by adding some script to the Digital Signage player of SiteKiosk Windows.

Scripting preparations:
We start by first creating a backup of the file "Start.html" under
"...\SiteKiosk\Skins\Public\ Startpages\SiteCaster".
Then open the file with an editor. It will look like this:

<html>
<head><meta http-equiv="X-UA-Compatible" content="IE=10" />
	<style>
		*
		{
			margin: 0;
			padding: 0;
			border: 0;
			font-family: sans-serif;
			font-size: 1em;
			font-weight: normal;
			font-style: normal;
			text-decoration: none;
		}
	</style>
</head>
<body scroll=no>
	<object id="Player" classid="clsid:719D9061-22DA-4D25-9BB9-116404372496" style="width: 100%;
		height: 100%; position: absolute; background: transparent;">
	</object>
</body>
</html>


Below the <object> tag (and before the closing </body> tag) we now will insert the required script part.
The first entry is for enabling the SiteKiosk Object Model on that page, needed to get the events for screensaver activated and deactivated.

<script>window.external.InitScriptInterface();</script>

The second entry is for loading a script that exposes the SiteCaster player functionality using an API called RequireJS (further information you will find in the article "Customize the SiteCaster Player in SiteKiosk").

<script src="../../External/require.js"></script>


Let’s come to the decisive part of the script.
First we load the "SiteCaster.js" script for controlling the SiteCaster object and ask it to give us a Player object of SiteCaster.

//load our dependent script (in this case it is only SiteCaster.js)
        require.config({
            baseUrl: "../.."
        });
        require(['Scripts/SiteCaster'],
                function (context, siteCaster) {
 
                    //ask it to give us a Player object of SiteCaster
					var player = siteCaster.Player(); …

Before we continue, we make sure that any scheduled campaign is stopped and check that a broadcast is loaded.

//switch off the scheduled playing of the broadcast in case it is activated
player.setAutoSchedule(false);

//check that the broadcast is loaded
player.broadcastLoaded(function () { …

 

Next we ask for all campaign items of the broadcast.

//get all campaign items of the current broadcast
var campaignItems = player.getCampaignItems();


Then we create a variable containing the ID of the first campaign.

//call the first Campaign of the array in the broadcast by id
var ToPlay = campaignItems[0]['id'];


And execute the command to play:

//play the fist campaign
player.play(ToPlay);


This function using the campaignEnd event makes sure that the campaign plays from the beginning again, when it has reached the end:

//play fist campaign again when campaign ends
player.campaignEnd(function (id) {player.play(ToPlay);});


The above just makes sure that our campaign plays in a loop, just as if using a "usual" scheduled campaign. This preparation is necessary for the following part, where we stop the campaign on screensaver start and play the campaign from the beginning, when the screensaver ends.

This script part will fire when the screensaver activates and is using the "OnScreenSaverBegin Event" of the SiteKiosk Object Model (remember we initialized it above) for getting the event.
Then it just uses player.stop(ToPlay);to stop the campaign playing.

//stop playing content when the screensaver activates
SiteKiosk.ScreenSaver.OnScreenSaverBegin = OnScreenSaverBegin;
	function OnScreenSaverBegin() {
        	player.stop(ToPlay);
}


To start the campaign from the beginning, when the screensaver stops, is very similar. It is using the "OnScreenSaverEnd Event" of the SiteKiosk Object Model and starts playing the campaign from start with player.play(ToPlay);

//start playing content when the screensaver deactivates
SiteKiosk.ScreenSaver.OnScreenSaverEnd = OnScreenSaverEnd;
function OnScreenSaverEnd() {
   player.play(ToPlay);
}


When we put all of this together, our page code now looks like this (download: Start.html (2.35 kb)):

<html>
<head><meta http-equiv="X-UA-Compatible" content="IE=10" />
	<style>
		*
		{
			margin: 0;
			padding: 0;
			border: 0;
			font-family: sans-serif;
			font-size: 1em;
			font-weight: normal;
			font-style: normal;
			text-decoration: none;
		}
	</style>
</head>
<body scroll=no>
	<!--object tag to embed the SiteCasterPlayer into the html page-->
	<object id="Player" classid="clsid:719D9061-22DA-4D25-9BB9-116404372496" style="width: 100%;
		height: 100%; position: absolute; background: transparent;">
	</object>
	
	<!--activate SiteKiosk Oject Model-->
	<script>window.external.InitScriptInterface();</script> 
	
	<!-- load a script that exposes the SiteCaster player functionality using an API called RequireJS (http://requirejs.org)-->
	<script src="../../External/require.js"></script>
    
	
	<script>
	//load our dependent script for RequireJS (in this case it is only SiteCaster.js)
        require.config({
            baseUrl: "../.."
        });
        require(['Scripts/SiteCaster'],
                function (context, siteCaster) {
 
                    //ask it to give us a Player object of SiteCaster
					var player = siteCaster.Player();
					
					//switch off the scheduled playing of the broadcast in case it is activated				
					player.setAutoSchedule(false);

					
					//check that the broadcast is loaded
                    player.broadcastLoaded(function () {
					
						//get all campaign items of the current broadcast									
						var campaignItems = player.getCampaignItems();
					
						//call the first Campaign of the array in the broadcast by id
						var ToPlay = campaignItems[0]['id'];
					
						//play the fist campaign
						player.play(ToPlay);
					
						//play fist campaign again when campaign ends
						player.campaignEnd(function (id) {player.play(ToPlay);});
						
					
						//stop playing content when the screensaver activates
						SiteKiosk.ScreenSaver.OnScreenSaverBegin = OnScreenSaverBegin;
						function OnScreenSaverBegin() {
							player.stop(ToPlay);
						}
					
						//start playing content when the screensaver deactivates
						SiteKiosk.ScreenSaver.OnScreenSaverEnd = OnScreenSaverEnd;
						function OnScreenSaverEnd() {
							player.play(ToPlay);
						}
                    
					});
                });
	</script>
</body>
</html>


Configuring SiteKiosk:
In the SiteKiosk configuration you just need to choose the "Player" at Start Page & Browser-->Digital Signage and deactivate the option "Suppress screensaver while playing".


On the Screensaver page, you configure the idle time before activating the screensaver and the content for the screensaver.
In this scenario I have configured the “SiteKiosk Player” with default settings, but you can of course also add other content to the SiteKiosk Player or even choose Digital Signage to display different content than is displayed in the main Digital Signage player.


Publishing the campaign:
To keep it simple for this example, we just publish a campaign with 3 pictures in a row. Of course you can also add any content of your choice, that can be displayed with the Digital Signage feature of SiteKiosk Windows (e.g. a video that will stop playing when the screensaver is activated and plays from the beginning when the screensaver is deactivated).


In the settings of the broadcast make sure you enable the checkbox "Disabled" because the campaign should only start to play when our script from above will execute the play command.


You can also add a second campaign to that broadcast, e.g. to be played during the screensaver, if you select the Digital Signage option on the Screensaver settings page of the SiteKiosk configuration. Make sure to explicitly set this campaign to be displayed during screensaver only and do not tick the "Disabled" option:


Our broadcast schedule for this example will look like this:

Now we publish the broadcast with our campaign:


After publishing the campaign the Digital Signage content displayed in SiteKiosk will always stop when the screensaver activates and start from the beginning when the screensaver will be deactivated.

Charging for Applications Opened from the SiteKiosk Windows Start Screen

In case you want to charge for applications that are started from an element on the Start Screen, you need to start the application using an html link instead of starting the application directly. Please note that only the Start Screen in combination with the IE browser engine allows the usage of payment features.

In the following example we will use Microsoft Word to demonstrate the process. You can apply this to any other application.

First open an editor like Notepad. Copy and paste the following html code:

<html>
   <head>
      <script type="text/javascript">
         <!--
            function StartApplication(){
                  window.external.InitScriptInterface();
                  SiteKiosk.ExternalApps.Run("C:\\Program Files (x86)\\Microsoft Office\\Office15\\WINWORD.EXE", true);
                  window.close();
            }
         //-->
      </script>
      <title>Word</title>
   </head>
   <body onload="StartApplication();">
   </body>
</html>

The SiteKiosk Object Model method Run starts the actual application. Change the path to whatever application you want to start and charge for. Make sure to use double backslashes in the path.

Save the above html code as an html file (e.g. word.html) and put it in the ..\SiteKiosk\html folder. Do the same for every application you want to start from the Start Screen. If for example you want to run 3 applications, you need 3 html files, one for each application.

Now open the configuration editor of SiteKiosk and add your application on the Applications page.

Next configure your payment device(s) and the service rates on the Payment Devices page.

Then switch over to the Start Page & Browser settings. Choose Internet Explorer as the browser engine. Select the Start Screen and click on Customize. In the new dialog go to Start Screen Editor and open the editor. In the template you want to use, add a new element and select Web link instead of Application link.

Add the html file that starts the desired application as a link and make sure to select a matching caption for the element.

For our example we would use file:///C:/Program Files (x86)/SiteKiosk/Html/Word.html.

Create a web link element for each of the applications you want to use.

Now SiteKiosk will charge for starting an application from the Start Screen.

Changing the User Agent of the SiteKiosk Windows Chrome Browser

To complement the 2013 blog post about changing the user agent string for the IE engine of SiteKiosk we will look at doing the same for the Chrome browser engine of SiteKiosk.

Please note, that you can easily add information to the standard user string by using the configuration options of SiteKiosk. Just go to Start Page & Browser -> Chrome Browser -> Customize -> Settings. There you can add SiteKiosk to the user agent header and also a freely customizable string that by default adds the Windows name of the computer ($ComputerName).

If you do not just want to add something to the default user agent you can open your SiteKiosk configuration with an editor. You will find a default setting that looks like this:

"userAgent": {
	"enabled": false,
	"full": "",

Using the default setting will result in something like this (depending on the SiteKiosk version used), when opening the W3Schools test page:

You can change the default values to this:

"userAgent": {
    "enabled": true,
    "full": "Whatever you want SiteKiosk to use as user agent string",

The attribute full is a string that you can copy a standard current or old Chrome user agent string to or any other existing or made up user agent string. Be aware that doing something like this can lead to problems on webpages, as they then assume a browser engine that in reality is not available, causing possible rendering issues.

The effect you will receive from doing the above change can be seen on the W3Schools page again:

Customizing the SiteKiosk Windows Chrome Browser Toolbar

Today we continue looking at options to customize the SiteKiosk Windows Chrome Browser. In last month's post we learned how to easily swap images for the buttons of the browser tooolbar. This time we are going a bit more into the details and learn how to change colors for individual buttons.

Before we start I want to remind you, that there is an even simpler way to change the overall colors of the SiteKiosk Windows Chrome Browser. Just go to Start Page & Browser -> Chrome Browser -> Customize -> Browser Design in the SiteKiosk configuration editor. There you can find 5 color pickers for a quick custom adjustment.

If you scroll down a little bit on that page, you can find an additional section that you can activate to create custom colors for every browser element.

The customizing options provided by the configuration editor are already quite comprehensive. We will be going a step further and change the colors of just one button to make this button standout from the rest and attract the user's attention.

To do that, we need to open and edit a JSON (JavaScript Object Notation) file that is used by the Chrome Browser of SiteKiosk Windows. The file content.json is located in the folder C:\Users\Public\SiteKiosk\data\content\local\files\projects\d97aa96b962543fcb39625a3f8e8d8fb\000000000000000000000000. Open it with an editor like Notepad++.

For the purpose of this demonstration we will continue to edit the individual button that you can configure on the configuration page for the Chrome browser toolbar: Start Page & Browser -> Chrome Browser -> Customize -> Browser Toolbar. In the content.json file look for this line:

"type": "content-custom-button-container",

This is the start of the definitions for the individual or custom button. A few lines down we can find a segment that looks like this:

"icon": {
	"src": "files/images/custom.svg",
	"color": "[[$root.colors.toolbarButton.icon]]",
	"hoverColor": "[[$root.colors.toolbarButton.iconHover]]",
	"pressedColor": "[[$root.colors.toolbarButton.iconPressed]]"
},
"backgroundImage": {
	"color": "[[$root.colors.toolbarButton.background]]",
	"hoverColor": "[[$root.colors.toolbarButton.backgroundHover]]",
	"pressedColor": "[[$root.colors.toolbarButton.backgroundPressed]]"
},

icon defines the image used for the button and the caption. src is the relative path to the image file so you can use your own image file without overwriting the existing one, color is the default color of the caption of the button, hoverColor is the color used when hovering the mouse over the button and pressedColor is used when the button is being clicked.

backgroundImage defines the colors for the background of the button. Again color is the default color of the caption, hoverColor is the color used when hovering the mouse of the button and pressedColor is used when the button is being clicked.

To assign your own color selection you can use the common notation format for colors: #FF9EDD.

Here is what an edited version of the above segment can look like:

"icon": {
	"src": "files/images/mycustom.svg",
	"color": "#FF9EDD",
	"hoverColor": "#BC7E87",
	"pressedColor": "#AE0000"
},
"backgroundImage": {
	"color": "#FFBE70",
	"hoverColor": "#FF8B51",
	"pressedColor": "#FF2600"
},

If you now prepare a configuration that includes an individual button you will get this result:

This is how the button looks by default:

Feel free to experiment with the values to create a custom browser experience that matches the needs of your kiosk project.