Defines a profile of RS
References the settings from DefaultSettings.xml. Only a subset of the settings will available to profile. We will need an attribute on the settings to indicate which ones are.
Application level toolbars
Do we have more than one explorer?
Application level menubars
Application level popup menus
Application level list views
There will be an XML file that defines which dialogs can be profiled and what parts can be profiled (the elements you see as children in the schema)
dialog elements are identify by id. We should have some way to indicate which elements we will allow to be hidden in a profile. How do we find items available to hide? Load all dialog resources? How do we find all dialogs? Where do we get the labels from?
Profiling which PGSDK and AVS charts are shown in the chart dialog. Used to control what charts from ChartTemplates.xml are shown in the chart picker dialog, if empty then show all
Profiles the propertySheets
In the future, we can add the option to have a custom URL for this
item can be idenfitied by one of (in priority) id, value, idsLabel.
Used to hide or show buttons in a toolbar. If set to show and shows nothing, it should hide the toolbar.
Defines a custom ordering of the toolbar buttons.
menubars, menu, menuPopup, toolbar and listView have an optional dialogId in current profiles. Why?
Profiles which properties appear in the property sheet.
Tab controls
We should change the tab control definition to be driven from an XML resource instead of from the HTML in irot.htm
Only applies the property visiblity to the named objects or namedSets, if not specified, applies to all properties