/*!
\page binding.html
\title Data Binding
\target binding
Data binding provides a declarative way of specifying the data associated with objects, as well as the relationship between data of different objects. For example, you could bind the text of a label to the value of a slider: as the value of the slider changed, the label would be automatically updated with the new value.
Bindings are indicated in Qml through the use of brackets: \c {}. For example, the following produces two Rects of equal size (\c rect2 is bound to the size of \c rect1):
\code
\endcode
There is also a special \c element, which is typically used to bind from the UI to the underlying UI model (see \l {Passing Data Between C++ and Qml} for an example of this). The bindings above could be expressed using the \c element as:
\code
\endcode
In addition to binding directly to a property, you can also bind to the results of expressions involving properties. For example:
\code
\endcode
Relevant items can also be bound to the contents of a model - see \l ListView for an example of this.
Data can be bound to C++ objects - see \l {C++ Data Binding}.
*/
/*!
\page qtbinding.html
\target qtbinding
\title C++ Data Binding
The QML mechanisms of \l {Data Binding} can also be used to bind Qt C++ objects.
The data binding framework is based on Qt's property system (see the Qt documentation for more details on this system). If a binding is meant to be dynamic (where changes in one object are reflected in another object), \c NOTIFY must be specified for the property being tracked. If \c NOTIFY is not specified, any binding to that property will be an 'intialization' binding (the tracking object will be updated only once with the initial value of the tracked object).
Relevant items can also be bound to the contents of a Qt model. For example, ListView can make use of data from a QListModelInterface-derived model. (QListModelInterface is part of the next generation Model/View architecture being developed for Qt.)
\section1 Passing Data Between C++ and Qml
Data binding provides one method of data transfer between C++ and Qml.
For example, lets say you want to implement a slider in Qml that changes the screen brightness of the device it is running on. You would start by declaring a brightness property on your QObject-derived class:
\code
class MyScreen : public QObject
{
Q_OBJECT
public:
MyScreen(QObject *parent=0);
Q_PROPERTY(int brightness READ brightness WRITE setBrightness NOTIFY brightnessChanged);
int brightness() const;
void setBrightness(int b);
...
signals:
void brightnessChanged();
private:
int m_brightness;
};
int brightness() const
{
return m_brightness;
}
void setBrightness(int b)
{
if (b != m_brightness) {
m_brightness = b;
emit brightnessChanged();
//set device brightness
...
}
}
\endcode
\note One important thing to keep in mind is that the changed signal should only be emitted when there is a real change ( \c b \c != \c m_brightness ), or you may get an infinite loop.
Next, make an instance of this class visible to the Qml bind engine:
\code
QFxView *view = new QFxView;
view->setXml("MyUI.qml");
MyScreen *screen = new MyScreen;
QmlBindContext *ctxt = view->bindContext();
ctxt->setProperty("screen", screen);
view->execute();
\endcode
\note Bindings must be made after setXml() but before execute().
Finally, in Qml you can make the appropriate bindings, so in \c "MyUI.qml":
\code
\endcode
The \l QBindableMap class provides a convenient way to make data visible to the bind engine.
*/