Difference between revisions of "Generating screens of the AVWizard"

From LinuxMCE
Jump to: navigation, search
 
m
Line 1: Line 1:
 +
[[Category: Development]]
 
<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>The class [[GenerateWizardConfigDefaults]] creates XML files coresponding to different screens of AVWizard. The corresponding mapping of Document View (which is the part stored in that XML files) are stored in [[WizardPagesFactory]].  
 
<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>The class [[GenerateWizardConfigDefaults]] creates XML files coresponding to different screens of AVWizard. The corresponding mapping of Document View (which is the part stored in that XML files) are stored in [[WizardPagesFactory]].  
  

Revision as of 18:45, 23 August 2009

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.
The class GenerateWizardConfigDefaults creates XML files coresponding to different screens of AVWizard. The corresponding mapping of Document View (which is the part stored in that XML files) are stored in WizardPagesFactory.

When you create a new page you should do the following:

- creates a file that correspond the mapping of the files with the document widgets content
- secondly the WizardWidgetsPage class returned by: WizardPagesFactory::CreatePredefinedWizardPage will load the XML file as the "static controls" and will create one class that implements the logic of it, which is derived  from WizardWidgetsPage.
 Classes like:
 WizardPageWelcome - first page that describes the first screen of the wizard
 WizardWidgetVideoRatio - screen that you choose resolution and refresh
 WizardPageVideoResolution - countdown contor that will let you keep the current resolution or goes forward
 WizardPageUISwitcher - a list that is stored the interface style
 WizardPageVideoOutput - choose the video connection you may use for your screen
 WizardPageVideoAdjustSize - choose the size for the screen of Orbiter
 WizardPageAudioConnection - choose the output connector for sound device. 
 WizardPageAudioVolume - choose the output sound device volume
 WizardPageDolbyTest - let user choose if it heards a dolby encoded sound
 WizardPageDTSTest -let user choose if it heards a DTS encoded sound
 WizardPageFinalSelections - let user informed of what the user choose