Class sap.ui.core.mvc.XMLViewModule: sap/ui/core/mvc/XMLView
A View defined using (P)XML and HTML markup.
Be aware that modifications of the content aggregation of this control are not supported due to technical reasons. This includes calls to all content modifying methods like
addContent> etc., but also the implicit removal of controls contained by the content aggregation. For example the destruction of a Control via the
destroy method. All functions can be called but may not work properly or lead to unexpected side effects.
On root level, you can only define content for the default aggregation, e.g. without adding the
<content> tag. If you want to specify content for another aggregation of a view like
dependents, place it in a child control's dependents aggregation or add it by using sap.ui.core.mvc.XMLView#addDependent.
sClassNameand enriches it with the information contained in
Constructor for a new mvc/XMLView.
Accepts an object literal
mSettings that defines initial property values, aggregated and associated objects as well as event handlers. See sap.ui.base.ManagedObject for a general description of the syntax of the settings object.
This class does not have its own settings, but all settings applicable to the base type sap.ui.core.mvc.View can be used.
|string||sId?||id for the new control, generated automatically if no id is given|
|object||mSettings?||initial settings for the new control|
Creates a new subclass of class sap.ui.core.mvc.XMLView with name
sClassName and enriches it with the information contained in
oClassInfo might contain the same kind of information as described in sap.ui.core.mvc.View.extend.
|string||sClassName||Name of the class being created|
|object||oClassInfo?||Object literal with information about the class|
|function||FNMetaImpl?||Constructor function for the metadata object; if not given, it defaults to |
|function||Created class / constructor function|
|sap.ui.base.Metadata||Metadata object describing this class|
Register a preprocessor for all views of a specific type.
The preprocessor can be registered for several stages of view initialization, for xml views these are either the plain "xml" or the already initialized "controls" , see sap.ui.core.mvc.XMLView.PreprocessorType. For each type one preprocessor is executed. If there is a preprocessor passed to or activated at the view instance already, that one is used. When several preprocessors are registered for one hook, it has to be made sure, that they do not conflict when beeing processed serially.
Note: Preprocessors work only in async views and will be ignored when the view is instantiated in sync mode by default, as this could have unexpected side effects. You may override this behaviour by setting the bSyncSupport flag to true.
|string|sap.ui.core.mvc.XMLView.PreprocessorType||sType||the type of content to be processed|
|string|function||vPreprocessor||module path of the preprocessor implementation or a preprocessor function|
|boolean||bSyncSupport||declares if the vPreprocessor ensures safe sync processing. This means the preprocessor will be executed also for sync views. Please be aware that any kind of async processing (like Promises, XHR, etc) may break the view initialization and lead to unexpected results.|
|boolean||bOnDemand?||ondemand preprocessor which enables developers to quickly activate the preprocessor for a view, by setting |
|object||mSettings?||optional configuration for preprocessor|