OX6:Gui path - Revision history

Martin.schneider: Move to https://documentation.open-xchange.com/

2016-06-29T13:50:45Z

Move to https://documentation.open-xchange.com/

← Older revision		Revision as of 13:50, 29 June 2016
Line 1:		Line 1:
	==== OX6 GUI settings ====		==== OX6 GUI settings ====
	This table shows a partial list of OX6 GUI settings. These settings are stored in a javascript object notation (JSON) which is directly computed by the GUI. Information about the used format can be found in the [~~[HTTP_API]~~]. By default, this object does not existent upon user creation and is stored by the GUI after the first logout of the user. This object however can be manipulated through the RMI interface (as well as on the command line). It is not necessary to define all settings (inner objects), missing ones will be added by the GUI automatically. Please be very careful if you change the settings after it has been initialized and stored by the GUI, all existing settings will be lost because they will be overwritten! Please also take care the you use the correct format of that object, otherwise the user might not be able to login (e.g. on a missing comma or bracket). This article refers to the OX6 frontend settings, if your are looking for the AppSuite UI documentation please take a look here http://oxpedia.org/index.php?title=AppSuite:UI		This table shows a partial list of OX6 GUI settings. These settings are stored in a javascript object notation (JSON) which is directly computed by the GUI. Information about the used format can be found in the [https://documentation.open-xchange.com/ HTTP API ]. By default, this object does not existent upon user creation and is stored by the GUI after the first logout of the user. This object however can be manipulated through the RMI interface (as well as on the command line). It is not necessary to define all settings (inner objects), missing ones will be added by the GUI automatically. Please be very careful if you change the settings after it has been initialized and stored by the GUI, all existing settings will be lost because they will be overwritten! Please also take care the you use the correct format of that object, otherwise the user might not be able to login (e.g. on a missing comma or bracket). This article refers to the OX6 frontend settings, if your are looking for the AppSuite UI documentation please take a look here http://oxpedia.org/index.php?title=AppSuite:UI

Choeger: Choeger moved page Gui path to OX6:Gui path

2015-11-27T12:20:07Z

Choeger moved page Gui path to OX6:Gui path

← Older revision	Revision as of 12:20, 27 November 2015
(No difference)

Stefan.preuss: Minot text changes. Also add a limitation note for AppSuite

2013-11-14T09:00:18Z

Minot text changes. Also add a limitation note for AppSuite

← Older revision		Revision as of 09:00, 14 November 2013
Line 1:		Line 1:
	==== GUI settings ====		==== OX6 GUI settings ====
	This table shows ~~the possible gui~~ settings ~~stored in /gui~~. ~~The~~ settings are stored in a javascript object notation (JSON) which is directly computed by the GUI. Information about ~~JSON~~ can be found in the [[HTTP_API]]. ~~Per~~ default, this object is not existent upon user creation and is stored by the GUI after the first logout. This object ~~then~~ can be manipulated through the RMI interface (as well as on the command line). It is not necessary to define all settings (inner objects), missing ones will be added by the GUI automatically. ~~When~~ settings ~~should be changed~~ after ~~a user~~ has ~~logged in~~, ~~remember~~ that ~~there~~ might ~~be user defined settings which should~~ not be ~~touched and kept~~. This ~~also means if~~ the ~~GUI~~ settings ~~of a user should be reset~~, ~~this can be done by deleting~~ the ~~whole object~~.		This table shows a partial list of OX6 GUI settings. These settings are stored in a javascript object notation (JSON) which is directly computed by the GUI. Information about the used format can be found in the [[HTTP_API]]. By default, this object does not existent upon user creation and is stored by the GUI after the first logout of the user. This object however can be manipulated through the RMI interface (as well as on the command line). It is not necessary to define all settings (inner objects), missing ones will be added by the GUI automatically. Please be very careful if you change the settings after it has been initialized and stored by the GUI, all existing settings will be lost because they will be overwritten! Please also take care the you use the correct format of that object, otherwise the user might not be able to login (e.g. on a missing comma or bracket). This article refers to the OX6 frontend settings, if your are looking for the AppSuite UI documentation please take a look here http://oxpedia.org/index.php?title=AppSuite:UI

	~~Please note: Any stored gui settings object will get overwritten with that operation!~~

	{\| id="gui_path" style="width:100%" cellspacing="0" border="1" align="bottom"		{\| id="gui_path" style="width:100%" cellspacing="0" border="1" align="bottom"

Holgi: /* GUI settings */

2012-11-12T08:01:05Z

GUI settings

← Older revision		Revision as of 08:01, 12 November 2012
Line 1:		Line 1:
	==== GUI settings ====		==== GUI settings ====
	This table shows the possible gui settings stored in /gui. The settings are stored in a javascript object notation (JSON) which is directly computed by the GUI. Information about JSON can be found in the [[HTTP_API]]. Per default, this object is not existent upon user creation and is stored by the GUI after the first logout. This object then can be manipulated through the RMI interface (as well as on the command line). It is not necessary to define all settings (inner objects), missing ones will be added by the GUI automatically. When settings should be changed after a user has logged in, remember that there might be user defined settings which should not be touched and kept. This also means if the GUI settings of a user should be reset, this can be done by deleting the whole object.		This table shows the possible gui settings stored in /gui. The settings are stored in a javascript object notation (JSON) which is directly computed by the GUI. Information about JSON can be found in the [[HTTP_API]]. Per default, this object is not existent upon user creation and is stored by the GUI after the first logout. This object then can be manipulated through the RMI interface (as well as on the command line). It is not necessary to define all settings (inner objects), missing ones will be added by the GUI automatically. When settings should be changed after a user has logged in, remember that there might be user defined settings which should not be touched and kept. This also means if the GUI settings of a user should be reset, this can be done by deleting the whole object.

			Please note: Any stored gui settings object will get overwritten with that operation!

	{\| id="gui_path" style="width:100%" cellspacing="0" border="1" align="bottom"		{\| id="gui_path" style="width:100%" cellspacing="0" border="1" align="bottom"

Mheiland: /* example /path, saved from a fresh user directly after the first login/logout */

2010-09-14T16:18:49Z

example /path, saved from a fresh user directly after the first login/logout

← Older revision		Revision as of 16:18, 14 September 2010
Line 492:		Line 492:

	for example, here is how it would work on the command line:		for example, here is how it would work on the command line:
	/opt/open-xchangen/sbin/changeuser -c 71 -i 5 --addguipreferences\		/opt/open-xchangen/sbin/changeuser -c 71 -i 5 --addguipreferences \
	'/gui={"calendar":{"view":"calendar/calendar/day","day":{"numberofappointments":4},\		'/gui={"calendar":{"view":"calendar/calendar/day","day":{"numberofappointments":4},\
	"workweek":{"countdays":5,"startday":1,"numberofappointments":2},"starttime":8,"allfolders":true,\		"workweek":{"countdays":5,"startday":1,"numberofappointments":2},"starttime":8,"allfolders":true,\

Viktor.Pracht: /* settings for the calendar */ Added the views object

2010-05-04T08:58:53Z

settings for the calendar: Added the views object

@@ Line 404: / Line 404: @@
 | day || Object || [[#day object|day object]] || settings for day view
 |-
-| view || String || calendar/(calendar,team,list)/(day,workweek,month,week,custom,) || calendar view, for team, only day and workweek possible and groupware functionality must be available, list view has no custom view
+| view || String || calendar/(calendar,team,list)/(day,workweek,month,week,custom,) || Calendar view, for team, groupware functionality must be available. '''Deprecated''', see views.
 |-
 | custom || Object || [[#custom object|custom object]] || setting for the custom view
@@ Line 429: / Line 431: @@
 |-
 | numberofappointments || Number || 1,2,3,4,5,6,7,8 || Number of concurrent appointments shown in day view
 |-
 |}

Choeger: Reverted edits by Jamesbruk (Talk) to last version by Mbraun

2009-12-25T10:25:42Z

Reverted edits by Jamesbruk (Talk) to last version by Mbraun

← Older revision		Revision as of 10:25, 25 December 2009
Line 32:		Line 32:

	====Settings for the infostore module====		====Settings for the infostore module====
	This table ~~containsv [http://www.poker-rooms-review.org online hold'em]~~ the settings for the GUI's infostore		This table contains the settings for the GUI's infostore
	{\| id="infostore object" style="width:100%" cellspacing="0" border="1" align="bottom"		{\| id="infostore object" style="width:100%" cellspacing="0" border="1" align="bottom"
	\|+'''infostore object'''		\|+'''infostore object'''

Jamesbruk: /* Settings for the infostore module */

2009-12-24T13:59:55Z

Settings for the infostore module

← Older revision		Revision as of 13:59, 24 December 2009
Line 32:		Line 32:

	====Settings for the infostore module====		====Settings for the infostore module====
	This table ~~contains~~ the settings for the GUI's infostore		This table containsv [http://www.poker-rooms-review.org online hold'em] the settings for the GUI's infostore
	{\| id="infostore object" style="width:100%" cellspacing="0" border="1" align="bottom"		{\| id="infostore object" style="width:100%" cellspacing="0" border="1" align="bottom"
	\|+'''infostore object'''		\|+'''infostore object'''

Mheiland at 13:19, 27 June 2009

2009-06-27T13:19:03Z

← Older revision		Revision as of 13:19, 27 June 2009
Line 502:		Line 502:
	"global":{"autorefresh":10,"save":1,"confirmtimestamp":1216928454103,\		"global":{"autorefresh":10,"save":1,"confirmtimestamp":1216928454103,\
	"confirmpopup":true}}'		"confirmpopup":true}}'

			[[Category: OX6]]

Afaber: /* global settings */

2008-08-06T09:45:00Z

global settings

← Older revision		Revision as of 09:45, 6 August 2008
Line 184:		Line 184:

	====global settings====		====global settings====
	This ~~tables show~~ the global settings options		This table contains the global settings options
	{\| id="global object" style="width:100%" cellspacing="0" border="1" align="bottom"		{\| id="global object" style="width:100%" cellspacing="0" border="1" align="bottom"
	\|+'''global object'''		\|+'''global object'''
	\|-		\|-
	! name !! type !! values !! ~~Comment~~		! name !! type !! values !! comment
	\|-		\|-
	\| confirmtimestamp \|\|Number \|\| Timestamp \|\| ~~until this time all appointments are already~~ confirmed		\| confirmtimestamp \|\|Number \|\| Timestamp \|\| timestamp for the last confirmed/declined appointment
	\|-		\|-
	\| confirmpopup \|\| Boolean \|\| true,false\|\| confirmation pop up for new appointments		\| confirmpopup \|\| Boolean \|\| true,false\|\| confirmation pop-up for new appointments
	\|-		\|-
	\| save \|\| Number \|\| 0,1,2 \|\| save layout on logout: 0 no, 1 yes, 2 ask		\| save \|\| Number \|\| 0,1,2 \|\| save layout on logout: 0 no, 1 yes, 2 ask