Appboard/2.5/builder/system administration/themes - Revision history

imported>Jason.nicholls at 07:38, 26 February 2015

2015-02-26T07:38:26Z

← Older revision		Revision as of 07:38, 26 February 2015
Line 75:		Line 75:
	[[Image:appboard-2.4-theme-editor.png\|frame\|center\|Theme Editor]]		[[Image:appboard-2.4-theme-editor.png\|frame\|center\|Theme Editor]]

	== ~~Migrating Custom Themes~~ ==		=== Theme Image Assets ===

	~~Themes consist of two parts:~~

	~~# Theme Configuration~~
	# Theme Assets~~: logo graphics, background images, etc..~~

	By default any theme configuration is automatically backed up when performing a full backup. Further, any theme assets located in <tt>[INSTALL_HOME]/server/webapps/enportal/visualizer/assets/custom/</tt> will also be included in any backup archive. Other theme assets existing elsewhere on the filesystem should be added to the custom export list to ensure the files are included in backup archives. See the [[appboard/2.5/admin/backup_and_recovery#Customizing_the_Export\|Customizing the Export]] section of the Backup & Recovery page for more information.

	To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.

	=~~= Theme Image Assets~~ ==

	{{Warning\|Do not modify the shipped image assets as these are not backed up and may be replaced on upgrade}}		{{Warning\|Do not modify the shipped image assets as these are not backed up and may be replaced on upgrade}}
Line 94:		Line 83:
	The following theme images are configurable by the theme editor:		The following theme images are configurable by the theme editor:

	* ''Global'' -> ''Background Image'': By default there is no background image configured. If this setting is enabled then it will take precedence over the ''Background Colors''. The selected image will be stretched to fit the available background space - which will depend on the screen resolution and browser dimensions for each client.		* "Global" -> "Background Image": By default there is no background image configured. If this setting is enabled then it will take precedence over the "Background Colors". The selected image will be stretched to fit the available background space - which will depend on the screen resolution and browser dimensions for each client.
	* ''Banner'' -> ''Logo Path'': By default this is the AppBoard logo, but can be changed. The default logo is 180 x 48 pixels and for convenience it is recommended to stick with 48 vertical pixels, however other Banner theme settings allow for changes to accommodate other sized logos.		* "Banner" -> "Logo Path": By default this is the AppBoard logo, but can be changed. The default logo is 180 x 48 pixels and for convenience it is recommended to stick with 48 vertical pixels, however other Banner theme settings allow for changes to accommodate other sized logos.

	To enable a custom image asset:		To enable a custom image asset:
Line 103:		Line 92:
	# Check the appropriate theme option (one of the above)		# Check the appropriate theme option (one of the above)
	# Use the magnifying icon to bring up the file explorer. Browse to the <tt>custom</tt> directory, find and select an image.		# Use the magnifying icon to bring up the file explorer. Browse to the <tt>custom</tt> directory, find and select an image.
	# Select ''OK'' to close the file explorer.		# Select "OK" to close the file explorer.
	# ''Save Changes'' in the theme editor.		# "Save Changes" in the theme editor.

			== Migrating Custom Themes ==

			Themes consist of two parts:

			# Theme Configuration
			# Theme Assets: logo graphics, background images, etc..

			By default any theme configuration is automatically backed up when performing a full backup. Further, any theme assets located in <tt>[INSTALL_HOME]/server/webapps/enportal/visualizer/assets/custom/</tt> will also be included in any backup archive. Other theme assets existing elsewhere on the filesystem should be added to the custom export list to ensure the files are included in backup archives. See the [[appboard/2.5/admin/backup_and_recovery#Customizing_the_Export\|Customizing the Export]] section of the Backup & Recovery page for more information.

			To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.

imported>Jason.nicholls: /* Replacing Logos and Background Image */

2015-02-26T07:35:24Z

Replacing Logos and Background Image

← Older revision		Revision as of 07:35, 26 February 2015
Line 86:		Line 86:
	To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.		To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.

	== ~~Replacing Logos and Background~~ Image ==		== Theme Image Assets ==

	~~=== Appboard Banner ===~~		{{Warning\|Do not modify the shipped image assets as these are not backed up and may be replaced on upgrade}}
	~~The default AppBoard logo location is: <tt>[<i>INSTALL_HOME</i>]/webapps/enportal/visualizer/~~assets~~/images/logo_banner.png</tt>~~

			Custom theme image assets should be placed into the <tt>[INSTALL_HOME]/server/enportal/visualizer/assets/custom/</tt> directory. This is to ensure the files are automatically included in backup archives.

	~~Perform the~~ following ~~steps to replace the default logo:~~		The following theme images are configurable by the theme editor:
	~~#Navigate to <tt>[<i>INSTALL_HOME</i>]/webapps/enportal/visualizer/assets/~~images~~</tt>~~
	~~#Open logo_banner.png in an image editor.~~
	~~#*The dimensions of the image~~ are ~~128x48 pixels, but~~ the ~~logo itself is only 32 pixels high~~
	~~#*Note~~: ~~The image height is the same height as the banner, so any desired padding should be added into the image~~
	~~#Paste desired logo into this file~~
	~~#Adjust padding to taste~~
	~~#Overwrite logo_banner.png with the new image~~

			* ''Global'' -> ''Background Image'': By default there is no background image configured. If this setting is enabled then it will take precedence over the ''Background Colors''. The selected image will be stretched to fit the available background space - which will depend on the screen resolution and browser dimensions for each client.
			* ''Banner'' -> ''Logo Path'': By default this is the AppBoard logo, but can be changed. The default logo is 180 x 48 pixels and for convenience it is recommended to stick with 48 vertical pixels, however other Banner theme settings allow for changes to accommodate other sized logos.

	~~Perform the following steps to replace the background~~ image:		To enable a custom image asset:
	#~~Create~~ the new ~~background image in an image editor~~
	#~~Save~~ the ~~new image~~ file to <tt>~~[<i>INSTALL_HOME</i>]/webapps/enportal/visualizer/assets/images/backgrounds~~</tt>		# Launch the Theme Editor
	~~#Do the following to configure the Theme to reference the new background~~ image:		# Edit an existing or create a new custom theme.
	#~~#Log in~~ to ~~AppBoard as an administrator~~		# Check the appropriate theme option (one of the above)
	~~##Launch~~ the ~~[[appboard/2~~.~~5/builder/system_administration/themes/editor_categories\|Theme Editor]]~~		# Use the magnifying icon to bring up the file explorer. Browse to the <tt>custom</tt> directory, find and select an image.
	#~~#Make sure you have created a custom Theme, and are editing that Theme (system Themes are not editable)~~		# Select ''OK'' to close the file explorer.
	~~##Under~~ the ~~"Global" section, check the "Background Image" box and edit the value to the location of your custom image, relative to [INSTALL_HOME]/server/webapps/enportal/visualizer/~~		# ''Save Changes'' in the theme editor.
	~~##*Example: assets/images/backgrounds/myImage~~.~~gif~~

imported>Mike.berman: add Replacing Logos and Background Image

2015-02-21T03:48:27Z

add Replacing Logos and Background Image

← Older revision		Revision as of 03:48, 21 February 2015
Line 85:		Line 85:

	To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.		To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.

			== Replacing Logos and Background Image ==

			=== Appboard Banner ===
			The default AppBoard logo location is: <tt>[<i>INSTALL_HOME</i>]/webapps/enportal/visualizer/assets/images/logo_banner.png</tt>


			Perform the following steps to replace the default logo:
			#Navigate to <tt>[<i>INSTALL_HOME</i>]/webapps/enportal/visualizer/assets/images</tt>
			#Open logo_banner.png in an image editor.
			#*The dimensions of the image are 128x48 pixels, but the logo itself is only 32 pixels high
			#*Note: The image height is the same height as the banner, so any desired padding should be added into the image
			#Paste desired logo into this file
			#Adjust padding to taste
			#Overwrite logo_banner.png with the new image


			Perform the following steps to replace the background image:
			#Create the new background image in an image editor
			#Save the new image file to <tt>[<i>INSTALL_HOME</i>]/webapps/enportal/visualizer/assets/images/backgrounds</tt>
			#Do the following to configure the Theme to reference the new background image:
			##Log in to AppBoard as an administrator
			##Launch the [[appboard/2.5/builder/system_administration/themes/editor_categories\|Theme Editor]]
			##Make sure you have created a custom Theme, and are editing that Theme (system Themes are not editable)
			##Under the "Global" section, check the "Background Image" box and edit the value to the location of your custom image, relative to [INSTALL_HOME]/server/webapps/enportal/visualizer/
			##*Example: assets/images/backgrounds/myImage.gif

imported>Jason.nicholls: /* Migrating Custom Themes */

2014-10-18T04:35:15Z

Migrating Custom Themes

← Older revision		Revision as of 04:35, 18 October 2014
Line 82:		Line 82:
	# Theme Assets: logo graphics, background images, etc..		# Theme Assets: logo graphics, background images, etc..

	By default any theme configuration is automatically backed up when performing a full backup. Further, any theme assets located in ''enportal/visualizer/assets/custom'' will also be included in any backup archive. Other theme assets existing elsewhere on the filesystem should be added to the custom export list to ensure the files are included in backup archives. See the [[appboard/2.5/admin/backup_and_recovery#Customizing_the_Export\|Customizing the Export]] section of the Backup & Recovery page for more information.		By default any theme configuration is automatically backed up when performing a full backup. Further, any theme assets located in <tt>[INSTALL_HOME]/server/webapps/enportal/visualizer/assets/custom/</tt> will also be included in any backup archive. Other theme assets existing elsewhere on the filesystem should be added to the custom export list to ensure the files are included in backup archives. See the [[appboard/2.5/admin/backup_and_recovery#Customizing_the_Export\|Customizing the Export]] section of the Backup & Recovery page for more information.

	To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.		To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.

imported>Andy.hopper: /* Migrating Custom Themes */

2014-09-02T20:14:29Z

Migrating Custom Themes

← Older revision		Revision as of 20:14, 2 September 2014
Line 82:		Line 82:
	# Theme Assets: logo graphics, background images, etc..		# Theme Assets: logo graphics, background images, etc..

	By default any theme configuration is automatically backed up when performing a full backup. Further, any theme assets located in ''enportal/visualizer/assets/custom'' will also be included in any backup archive. Other theme assets existing elsewhere on the filesystem should be added to the custom export list to ensure the files are included in archives. See the [[appboard/2.5/admin/backup_and_recovery#Customizing_the_Export\|Customizing the Export]] section of the Backup & Recovery page for more information.		By default any theme configuration is automatically backed up when performing a full backup. Further, any theme assets located in ''enportal/visualizer/assets/custom'' will also be included in any backup archive. Other theme assets existing elsewhere on the filesystem should be added to the custom export list to ensure the files are included in backup archives. See the [[appboard/2.5/admin/backup_and_recovery#Customizing_the_Export\|Customizing the Export]] section of the Backup & Recovery page for more information.

	To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.		To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.

imported>Andy.hopper: /* Migrating Custom Themes */

2014-09-02T20:14:07Z

Migrating Custom Themes

← Older revision		Revision as of 20:14, 2 September 2014
Line 82:		Line 82:
	# Theme Assets: logo graphics, background images, etc..		# Theme Assets: logo graphics, background images, etc..

	By default any theme configuration is automatically backed up when performing a full backup. Further, any theme assets located in ''enportal/visualizer/assets/custom'' will also be included in any backup archive. ~~If other~~ theme assets ~~exist~~ elsewhere on the filesystem~~, then these~~ should be added to the custom export list to ensure the files are included in archives. See the [[appboard/2.5/admin/backup_and_recovery#Customizing_the_Export\|Customizing the Export]] section of the Backup & Recovery page for more information.		By default any theme configuration is automatically backed up when performing a full backup. Further, any theme assets located in ''enportal/visualizer/assets/custom'' will also be included in any backup archive. Other theme assets existing elsewhere on the filesystem should be added to the custom export list to ensure the files are included in archives. See the [[appboard/2.5/admin/backup_and_recovery#Customizing_the_Export\|Customizing the Export]] section of the Backup & Recovery page for more information.

	To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.		To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.

imported>Andy.hopper: /* Migrating Custom Themes */

2014-09-02T20:13:14Z

Migrating Custom Themes

← Older revision		Revision as of 20:13, 2 September 2014
Line 82:		Line 82:
	# Theme Assets: logo graphics, background images, etc..		# Theme Assets: logo graphics, background images, etc..

	By default any theme configuration is automatically backed up when performing a full backup. Further, any theme assets located in 'enportal/visualizer/assets/custom' will also be included in any backup archive. If other theme assets exist elsewhere on the filesystem, then these should be added to the custom export list to ensure the files are included in archives. See the [[appboard/2.5/admin/backup_and_recovery#Customizing_the_Export\|Customizing the Export]] section of the Backup & Recovery page for more information.		By default any theme configuration is automatically backed up when performing a full backup. Further, any theme assets located in ''enportal/visualizer/assets/custom'' will also be included in any backup archive. If other theme assets exist elsewhere on the filesystem, then these should be added to the custom export list to ensure the files are included in archives. See the [[appboard/2.5/admin/backup_and_recovery#Customizing_the_Export\|Customizing the Export]] section of the Backup & Recovery page for more information.

	To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.		To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.

imported>Andy.hopper: /* Migrating Custom Themes */

2014-09-02T20:13:02Z

Migrating Custom Themes

← Older revision		Revision as of 20:13, 2 September 2014
Line 82:		Line 82:
	# Theme Assets: logo graphics, background images, etc..		# Theme Assets: logo graphics, background images, etc..

	By default any theme configuration is automatically backed up when performing a full backup. ~~For~~ other theme assets on the filesystem then these should be added to the custom export list to ensure the files are included in archives. See the [[appboard/2.5/admin/backup_and_recovery#Customizing_the_Export\|Customizing the Export]] section of the Backup & Recovery page for more information.		By default any theme configuration is automatically backed up when performing a full backup. Further, any theme assets located in 'enportal/visualizer/assets/custom' will also be included in any backup archive. If other theme assets exist elsewhere on the filesystem, then these should be added to the custom export list to ensure the files are included in archives. See the [[appboard/2.5/admin/backup_and_recovery#Customizing_the_Export\|Customizing the Export]] section of the Backup & Recovery page for more information.

	To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.		To migrate a custom theme to another AppBoard instance altogether then the Import/Export tool can be used, but please note this only includes theme configuration and the theme assets will have to be copied separately. Refer to the [[appboard/2.5/builder/system_administration/import_export\|Import/Export]] documentation for more information. It's also important to include any themes which the exported theme may be dependent on, if not directly dependent on a base theme.

imported>Jason.nicholls: /* Using the Theme Editor */

2014-07-30T11:59:47Z

Using the Theme Editor

← Older revision		Revision as of 11:59, 30 July 2014
Line 70:		Line 70:
	By selecting a different <b>Theme Template</b>, you will swap out the base values used by the current Theme. Any overrides configured as part of your new Theme will persist; however, the values used in your overrides may no longer make sense after you have switched from a "Dark" theme to a "Light" theme.		By selecting a different <b>Theme Template</b>, you will swap out the base values used by the current Theme. Any overrides configured as part of your new Theme will persist; however, the values used in your overrides may no longer make sense after you have switched from a "Dark" theme to a "Light" theme.

	Refer to the [[appboard/2.5/builder/themes/editor_categories\|Theme Editor Categories]] page to explain the grouping categories for configurable options. Also refer to the [[appboard/2.5/builder/themes/editor_controls\|Theme Editor Controls]] to describe the types of controls available for theme options.		Refer to the [[appboard/2.5/builder/system_administration/themes/editor_categories\|Theme Editor Categories]] page to explain the grouping categories for configurable options. Also refer to the [[appboard/2.5/builder/system_administration/themes/editor_controls\|Theme Editor Controls]] to describe the types of controls available for theme options.

imported>Jason.nicholls: moved appboard/2.5/builder/themes to appboard/2.5/builder/system administration/themes

2014-07-30T11:59:11Z

moved appboard/2.5/builder/themes to appboard/2.5/builder/system administration/themes

← Older revision	Revision as of 11:59, 30 July 2014
(No difference)