Difference between revisions of "AVWizard Description Language"
Langstonius (Talk | contribs) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[category: Programmer's Guide]] | |
| + | 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. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
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. | ||
| Line 29: | Line 23: | ||
Command parsing | Command parsing | ||
| − | The command parsing is a stack, which calls a command and | + | 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 36: | Line 30: | ||
Following commands will destroy the stack: | Following commands will destroy the stack: | ||
$next; $previous; CurrentControl.OnClose | $next; $previous; CurrentControl.OnClose | ||
| − | The next coomand | + | The next coomand destroys the screen, which cleans up the all commands. |
Latest revision as of 03:38, 21 June 2008
Every screen will be stored in a file with SDF or XML extension: 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 removes 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 destroys the screen, which cleans up the all commands.
