This reverts commit a454ff7f.

This patch should follow patch 91fc9b18



Change-Id: I5e26da1d967f8880d73e32ad5a76c59bedf7a065
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

This reverts commit c5270bdb7261deaeed13c49ba8b4c17825b5619b

Since we reverted Change Ia638064f: Return infinity instead of -1 as a default value for max sizes, we have to revert this one as it depends on it.

Change-Id: I765b67ac7c77074bbcf75fd3010d146d2e00a0b0
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

With commit 16558ac7


Layout.maximumWidth and Layout.maximumHeight now returns
Number.POSITIVE_INFINITY instead of -1.
As described in that commit, comparisons against those properties
does not need any special handling for -1 anymore.

Change-Id: I8d4bba0fa87f9c67ac30dd40a8be8cb99abba283
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>

If the user sets Layout.maximumWidth on the fillWidth item, we now
respect it. This can potentially make the splitview look buggy, since
the fillWidth item might then be restrained from filling out remaining
space. The same with the height of each item; you can now control the
maximum height. This means that each item can end up with a different
height. The upshot is that if you add items to a splitview that
cannot grow, splitview will not try to resize it.

Change-Id: If1cc82aefa939898a3b159da6b006f95af42599f
Reviewed-by: Jan Arve Sæther <jan-arve.saether@digia.com>

Rename variables to the new Layout terminology, to ease
future maintenance/understanding of the code.

Change-Id: I619f62a0280238fafefe261fae3f00eb575bb699
Reviewed-by: Jan Arve Sæther <jan-arve.saether@digia.com>

This function was added in a previous patch, so reuse it
for already existing code.

Change-Id: Icd5daf195af7e249d4273bbc32a290bed5f0eaa5
Reviewed-by: Jan Arve Sæther <jan-arve.saether@digia.com>

Set the implicit size of the SplitView based on the sizes of the
split items.

Change-Id: I775b938215216831d10cb50868e4c6733e157eeb
Reviewed-by: Jan Arve Sæther <jan-arve.saether@digia.com>

Task-number: QTBUG-30318
Change-Id: If3916f3250f202a5da4b1f8034ecfba984367af3
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Reviewed-by: Jan Arve Sæther <jan-arve.saether@digia.com>
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

This regressed due to 2ed163c6



Change-Id: Ib566dec33dad2f5dad5894ff94bd5ce09ecd515a
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Change-Id: I2eaaf7e82351e70a742eeadc32b8e1f8655a02c1
Reviewed-by: Caroline Chao <caroline.chao@digia.com>

Concerning vocab., punctuation, syntax and/or Writing Guidelines.
Corrected whitespace issues.
Replaced "if" with "whether" in Slider.qml

Task-number: QTBUG-30318

Change-Id: I0e0e8d2b807f0a6534deb2caa6dbee7eb206f43b
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
Reviewed-by: Martin Smith <martin.smith@digia.com>
Reviewed-by: Laszlo Papp <lpapp@kde.org>

..to Layout.fill{Width,Height}

This property now takes a bool, which enables you to write
  Layout.fillWidth: true

instead of
  Layout.horizontalSizePolicy: Layout.Expanding

Change-Id: Icf2e0dc4757938489908b8997d6c4e80c8be1c50
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

This will be set to 'true' when any of the splitter handles are
being dragged

Change-Id: I715f8107ff1844b97df27d649f2d48785476adf9
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Change-Id: If9df032c76e36f385aacd30cc31d6f02574c6f11
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>

Those connections are sometimes called after the SplitView has
been destructed and it causes warnings (i.e. tst_splitview autotests).

Change-Id: I42ae333e72c01edba78f69bb1e9de8b4f85dea2c
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>

Found this bug while replicating the Creator layout.
Aparently the content item is the parent of children so it should
fill the contents of the SplitView, otherwise it will report a
width and height of 0.

Change-Id: I47a8e6cbecf8642e2d133a0be0dce0305a167c0c
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>

Change-Id: Ifa95b8db73b78c3b46d7d18bc55aa06d2569c89e
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

It now uses the gridlayoutengine from graphicsview, which
also gives us a well tested grid layout engine almost for
free.

Change-Id: I939ae4d2b321c8079935ff3374e8e5d10d02384b
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

If the SplitView was initially hidden, and told to
show later, the handles ended up at wrong positions.
This patch will fix this.

Change-Id: Ia21fa1efcf30c36bf18e0d4f3ab0813c6b79afcc
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

Also removes the RangeTab from the Gallery example, since its controls
use containsMouse and are no longer different from the same set of
sliders on the control tab. Adding MouseAreas to each control in
RangeTab to achieve the same animation would clutter the example with
boilerplate code.

Change-Id: I80d6f3bbf1b73229f4d0ae99dd2a65bc083e7099
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Most of the documentation was there already, just not using proper qdoc format.

Change-Id: Ia28a0da3b20151202cafdbc1b535a1921a48b1a6
Reviewed-by: Caroline Chao <caroline.chao@digia.com>

Change-Id: I1db05195ada0b798a632da04fb256f030c894560
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

We want to use the same license as the other Qt modules.
QML files stay as BSD for now.

Change-Id: I10b1484f5ab0dfe2138ff7e045d0ecfd85556aa1
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

Change-Id: Icc61dbfc74cc2a303b9847e7d2c7ace4a9002046
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

This change will remove the old splitter implementation, and
replace it with a new Splitter.qml that can be either
horizontal or vertical.

Change-Id: Ic02f3654bf92bdeecbc47096f4f45135dd484368
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>