AVWizard Description Language - Revision history

Langstonius at 02:38, 21 June 2008

2008-06-21T02:38:03Z

←Older revision		Revision as of 02:38, 21 June 2008
Line 1:		Line 1:
			[[category: Programmer's Guide]]
	Every screen will be stored in a file with SDF or XML extension:		Every screen will be stored in a file with SDF or XML extension:
	'''''SDF = Screen Definition Page'''''.		'''''SDF = Screen Definition Page'''''.

Juliet at 15:43, 16 March 2007

2007-03-16T15:43:30Z

←Older revision		Revision as of 15:43, 16 March 2007
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>Every screen will be stored in a file with SDF or XML extension:		Every screen will be stored in a file with SDF or XML extension:
	'''''SDF = Screen Definition Page'''''.		'''''SDF = Screen Definition Page'''''.

Juliet at 08:37, 15 March 2007

2007-03-15T08:37:43Z

←Older revision		Revision as of 08:37, 15 March 2007
Line 22:		Line 22:
	Command parsing		Command parsing

	The command parsing is a stack, which calls a command and ~~remove~~ the command after.		The command parsing is a stack, which calls a command and removes the command after.

	The command: $generate_event push commands in pending state.		The command: $generate_event push commands in pending state.
Line 29:		Line 29:
	Following commands will destroy the stack:		Following commands will destroy the stack:
	$next; $previous; CurrentControl.OnClose		$next; $previous; CurrentControl.OnClose
	The next coomand ~~destroy~~ the screen, which ~~clean~~ up the all commands.		The next coomand destroys the screen, which cleans up the all commands.

Wikiadmin at 06:45, 13 April 2006

2006-04-13T06:45:22Z

←Older revision		Revision as of 06:45, 13 April 2006
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>Every screen will be stored in a file with SDF extension:		<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>Every screen will be stored in a file with SDF or XML extension:
	'''''SDF = Screen Definition Page'''''.		'''''SDF = Screen Definition Page'''''.

	Every event called to a ~~child~~ control, will be called to the ~~parent~~. Events will be parsed by control and if the event is not known, there should be no suitable code, else will call the default action.		Every event called to a parent control, will be called to the children. Events will be parsed by control and if the event is not known, there should be no suitable code, else will call the default action.

	Saving informations, set up the wizard defaults.		Saving informations, set up the wizard defaults.

	Control definition:		Control definition is over one SettingsDictionary means that one control has:
			Name: String
			Type: String
			Attributes which are pears of Name and Value (both String types).

	~~'''object''' ControlName: <ControlType>~~

	~~[Propery = Value]~~

	~~Event: [[[[action1;] action2; ] .... ;] action_n]~~

	~~['''object''' Child: <Control Type>~~

	~~<Child definitions>~~

	~~'''End''']~~
	~~'''End'''~~

	See [[AVWizard script based user callable events]] for possible actions that may call one event.		See [[AVWizard script based user callable events]] for possible actions that may call one event.

Wikiadmin at 08:08, 11 April 2006

2006-04-11T08:08:52Z

←Older revision		Revision as of 08:08, 11 April 2006
Line 19:		Line 19:

	'''End''']		'''End''']
	~~end~~		'''End'''

			See [[AVWizard script based user callable events]] for possible actions that may call one event.

	Every ListBox and Button will be saved to the next page in a list of stored options.		Every ListBox and Button will be saved to the next page in a list of stored options.

Wikiadmin at 08:07, 11 April 2006

2006-04-11T08:07:47Z

←Older revision		Revision as of 08:07, 11 April 2006
Line 9:		Line 9:

	'''object''' ControlName: <ControlType>		'''object''' ControlName: <ControlType>
	[Propery = Value]
	Event: [[[[action1;] action2; ] .... ;] action_n]		[Propery = Value]

			Event: [[[[action1;] action2; ] .... ;] action_n]

	['''object''' Child: <Control Type>		['''object''' Child: <Control Type>

	<Child definitions>		<Child definitions>

	'''End''']		'''End''']
	end		end

Wikiadmin at 08:06, 11 April 2006

2006-04-11T08:06:21Z

←Older revision		Revision as of 08:06, 11 April 2006
Line 1:		Line 1:
	<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>		<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>Every screen will be stored in a file with SDF extension:
	Every screen will be stored in a file with SDF extension:		'''''SDF = Screen Definition Page'''''.
	SDF = Screen Definition Page.

	Every event called to a child control, will be called to the parent. Events will be parsed by control and if the event is not known, there should be no suitable code, else will call the default action.		Every event called to a child control, will be called to the parent. Events will be parsed by control and if the event is not known, there should be no suitable code, else will call the default action.
Line 9:		Line 8:
	Control definition:		Control definition:

	object ControlName: <ControlType>		'''object''' ControlName: <ControlType>
	[Propery = Value]		[Propery = Value]
	Event: [[[[action1;] action2; ] .... ;] action_n]		Event: [[[[action1;] action2; ] .... ;] action_n]
	[object Child: <Control Type>		['''object''' Child: <Control Type>
	<Child definitions>		<Child definitions>
	End]		'''End''']
	end		end

Wikiadmin at 07:42, 11 April 2006

2006-04-11T07:42:15Z

New page

<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>
Every screen will be stored in a file with SDF extension:
SDF = Screen Definition Page.

Every event called to a child control, will be called to the parent. Events will be parsed by control and if the event is not known, there should be no suitable code, else will call the default action.

Saving informations, set up the wizard defaults.

Control definition:

object ControlName: <ControlType>
[Propery = Value]
Event: [[[[action1;] action2; ] .... ;] action_n]
[object Child: <Control Type>
<Child definitions>
End]
end

Every ListBox and Button will be saved to the next page in a list of stored options.
Stored informations are next:
Page/Control/Option

At $next event, every control will be saved, and at the $previous command every control with current page will be removed.

Command parsing

The command parsing is a stack, which calls a command and remove the command after.

The command: $generate_event push commands in pending state.

Exceptional cases:
Following commands will destroy the stack:
$next; $previous; CurrentControl.OnClose
The next coomand destroy the screen, which clean up the all commands.