scripting » Revisions »

Differences

This shows you the differences between the selected revisions of the page.

2016-03-30		2016-05-30
styling (martin)		non isolated script is not portable (martin)
	Line 146:		Line 146:
	The advantage is that you can use graphical interface to [[faq_script_ini\|configure options for which there are no script commands]].		The advantage is that you can use graphical interface to [[faq_script_ini\|configure options for which there are no script commands]].

-	The disadvantage is that change to configuration in graphical mode may break your script (common example is enabling //[[ui_synchronize\|Existing files only]]// option for [[task_synchronize_full\|synchronization]]).	+	The disadvantage is that change to configuration in graphical mode may break your script (common example is enabling //[[ui_synchronize\|Existing files only]]// option for [[task_synchronize_full\|synchronization]]). Also the script is not portable to other machines, when it relies on an external configuration.

-	If you want to protect your script from such inadvertent change, you should isolate its configuration from graphical mode explicitly.	+	If you want to protect your script from such inadvertent change or if you want to make the script portable, you should isolate its configuration from graphical mode explicitly.

	The best way to do that is to configure all the options you need using script commands only (''[[scriptcommand_option\|option]]'' command, switches of other commands, [[session_url\|session URL]]), or if no such command is available, using [[rawsettings\|raw site settings]] and [[rawconfig\|raw configuration]]. Finally force scripting mode to start with the default configuration using ''[[commandline#configuration\|/ini=nul]]'' command-line parameter.		The best way to do that is to configure all the options you need using script commands only (''[[scriptcommand_option\|option]]'' command, switches of other commands, [[session_url\|session URL]]), or if no such command is available, using [[rawsettings\|raw site settings]] and [[rawconfig\|raw configuration]]. Finally force scripting mode to start with the default configuration using ''[[commandline#configuration\|/ini=nul]]'' command-line parameter.