Difference between revisions of "AVWizard Description Language"
| 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 | + | 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). | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
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. | ||
Revision as of 07:45, 13 April 2006
| 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. |
SDF = Screen Definition Page.
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.
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).
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. 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.
