| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Layout examples for QML are also cleaned up a bit.
Layouts test removed, and LayoutItem test added, to clarify what we
support.
Reviewed-by: Michael Brasser
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Where you would have written
x: NumberAnimation {}
y: Behavior {}
you now must write
NumberAnimation on x {}
Behavior on y {}
This change also makes the parser more strict with respect to multiple
assignments to a single property - they're no longer allowed. For example
this
x: 10
x: 11
is now an error.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
has proven to be confusing in practice.
property/target and properties/targets will be functionally equivilant
(the only distinction being singular/plural). In a transition these
properties can be used for both 'matching' and explicit animation
based on whether a 'to' value is supplied.
The documentation, tests, examples and demos have been updated as well.
|
| |
|
|\
| |
| |
| | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | |
|
|/ |
|
|
|
|
|
|
|
| |
They are only for the positioner's position changes, other changes are
under the designers control and the designer should animate them.
Task-number: QT-2239
|
| |
|
| |
|
|
|
|
| |
QFxBasePositioner still exists though.
|
| |
|
|
Interim progress on fixing up the positioners.
- Removes margins and setting and implicit size
- Purges the word 'layout' from the source files
- Fixes a bug with the grid positioner, it works now
- Cleaned up the code somewhat.
Also adds some basic examples which demonstrate that it (mostly) works.
Be warned that practically all the comments are woefully out of date.
|