Difference between revisions of "AVWizard developer's point of view"
From LinuxMCE
| Line 5: | Line 5: | ||
AVWizard has the next working steps: | AVWizard has the next working steps: | ||
| − | - | + | - [[Generating screens of the AVWizard]] (in the /tmp folder as XML files) |
- load one by one depending of the needs of running ([[Main AVWizard]]). | - load one by one depending of the needs of running ([[Main AVWizard]]). | ||
That two steps may be splitted in the future in two separately applications, that will make it more customisable and to not make it more "redundant code" like: defining object, '''save/load''' operations restore objects. | That two steps may be splitted in the future in two separately applications, that will make it more customisable and to not make it more "redundant code" like: defining object, '''save/load''' operations restore objects. | ||
The XML files keeps only the display representations of the data. The factory creates the coresponding objects in a WizardWidget class which contains a tree of WizardWidgets that has as much childs as we are used. | The XML files keeps only the display representations of the data. The factory creates the coresponding objects in a WizardWidget class which contains a tree of WizardWidgets that has as much childs as we are used. | ||
Revision as of 13:07, 6 October 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. |
- SDL (SDL_image, SDL_rotozoom, etc.) - libXML2 - network code
AVWizard has the next working steps:
- Generating screens of the AVWizard (in the /tmp folder as XML files) - load one by one depending of the needs of running (Main AVWizard).
That two steps may be splitted in the future in two separately applications, that will make it more customisable and to not make it more "redundant code" like: defining object, save/load operations restore objects. The XML files keeps only the display representations of the data. The factory creates the coresponding objects in a WizardWidget class which contains a tree of WizardWidgets that has as much childs as we are used.
