* List all applicable attached properties for each layout
* Move the stuff that describes min,pref and max sizes from GridLayout
  to the Layout docs.
* Document that all layouts \inherits Item. (Even if they don't directly
  inherit, this is consistent with how the positioners are documented)
* Add some links to Row, Column and Grid where appropriate
* Use \qmlattachedproperty instead of \qmlproperty for the attached
  properties. (Again, consistent with how the Positioners attached
  properties are documented)
* Change POSITIVE_INFINITE to the correct POSITIVE_INFINITY

Change-Id: Ia9272faa479b48a97300b031402c0380ca113d7b
Reviewed-by: Caroline Chao <caroline.chao@digia.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>

Change-Id: I1ee810dfcd57fd9ff7ddf65c87208c8b457f755e
Reviewed-by: Nico Vertriest <nico.vertriest@digia.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>

This reverts commit 91fc9b18

.

This patch got reverted because it broke the basiclayouts example on Mac OS.

However, the bug was in the basiclayouts example, so we can still add
this patch.

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

This reverts commit a4158c97d84d5c76126307213baf22d12babdbc2

This commit breaks the basiclayouts example so I am reverting it until we have a revised ifx.

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

This was a bit inconsistent, because in the case of a Rectangle its
Layout.maximumWidth would return -1 by default (which was supposed to
be interpreted as infinity) However, since the maximumWidth propagated
up to the layout, the layout.Layout.maximumWidth would return
1000000000. Adding two Rectangles to the layout would make
layout.Layout.maximumWidth return 2000000000, and adding a third item
with Layout.maximumWidth:1 would make layout.Layout.maximumWidth
return 2000000001

With this change, since infinity + number = infinity, everything
that can grow to infinity will just return infinity.

In addition a developer can now more intuitively do comparisons
like this:

if (value > Layout.minimumWidth && value < Layout.maximumWidth)

instead of

if ((value == -1 || value > Layout.minimumWidth) &&
    (value != -1 && value < Layout.maximumWidth))

Now, as a bonus, it becomes less consistent to set an attached
(min,max) property to -1 in order to reset it to its implicit value.

This also fixes a documentation issue with regards to the attached
Layout.{min|max}imum{Width|Height} properties. It only told the story
correct if the item was not a layout, and updates the docs for the max
sizes to mention that it returns Number.POSITIVE_INFINITY

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

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

This issue refactors how size hints are propagated up layout
hierarchies. It fixes several problems:

1. Do not overwrite explicitly set size hints when propagating them
   (Covered by test_sizeHint(propagateNone) )
2. Propagate size hints immediately when they are changed.
   Previously, this was in an inconsistent state, since for some
   operations (such as implicitWidth changes) it would immediately
   propagate through an explicit call to propagateSizeHints. However,
   changes to other properties such as Layout.minimumWidth would simply
   call invalidate(), causing the propagation to be postponed until the
   layout got rearranged.
3. Do not propagate size hints from rearrange. This could potentially
   make rearrange() unnecessary slow.
4. Only use the fallback to width/height the *first* time the size hint
   is queried. This had the unfortunate consequence when a
   Layout.preferredWidth was reset back to -1 it could end up querying
   the width again (due to layout resizing, this could at this point be
   different than what was specified in the QML file). This is still
   not bullet proof, but AFAIK there is no bullet-proof way, since there
   is no way of retrieving the original value that 'width' was bound to
   in the QML file.
   (Covered by test_sizeHintPropagationCount)

The performance characteristics for this change should be that it will
make resizing of layouts faster, but will make dynamic changes to the
layout slower (since it has to propagate the size hints every time a
property is changed).

Change-Id: I3dd818f6f7504908534eb5b22413fbeba1877985
Task-number: QTBUG-30773
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>

This makes our documentation slightly better (no need to document
default value of Layout.maximumWidth to 100000000)

In addition, the developer can now specify a preferredWidth/Height of 0
and it will actually be respected. (Previously there was no way of
distinguishing between Layout.preferredWidth not set, and set to 0.)

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

This allows us to move some docs out of GridLayout and into the Layout
documentation.
Did some additional polishing of documentation.

Change-Id: I49425d7f6b30b48527fb98ac010b094bf02c00a8
Reviewed-by: Martin Smith <martin.smith@digia.com>

Alignment is per-item

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

setupItemLayout was supposed to do initialization on each item before
it got added to the layout, but all it did was to add the attached
property to the item, which is really not needed anymore.
The layout code does not work under the assumption that each item has
the attached property anyway, so we can remove it. (And in addition
avoid some potential allocations)

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

Items will be laid sequentially in the grid, either in LeftToRight
mode or TopToBottom mode (depending on the value of the flow property)

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

..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>

Since we also rearrange in geometryChanged(), this should ensure
that we recurse down and arrange all sublayouts.

This assumes that objects are constructed in bottom-up order.
(That's what componentComplete() indicates.)

Previously we would risk rearranging sublayouts several times:
1. Sublayout got componentComplete -> geometryChanged -> rearrange()
2. Parent layout got componentComplete -> geometryChanged -> rearrange()
3. Since the sublayout was a layout item of the parent layout it could
   get a geometry change again, causing it to rearrange again.

This also fixes the issue where the implicitWidth/Height of the layout
was not immediately set after componentComplete, which could cause it
to get the wrong initial size.

Change-Id: I63a35dd934cd3ace01fab6319333d531631a6f4e
Reviewed-by: Frederik Gladhorn <frederik.gladhorn@digia.com>

If the item had an attached Layout property, but had no size policy
set, the size policy became Fixed for layouts, since it was the
default in QQuickLayoutAttached

Change-Id: I7e317737498548895561b1953e3ad731101c3e86
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@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>

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>

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

Including QT_BEGIN_NAMESPACE, QT_END_NAMESPACE, QT_BEGIN_HEADER
and QT_END_HEADER.

Change-Id: I9040bdf097d229ba897ada799f72cd9bfc80c844
Reviewed-by: Liang Qi <liang.qi@digia.com>

Change-Id: I58c6f143de8d074fe2b382eff524500c6a8270ea
Reviewed-by: Liang Qi <liang.qi@digia.com>

Change-Id: Ibf752d64399c6bd4bf5519aab330a9eacf6bb91b
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>

Still missing sth from qmake, it doesn't support non c++ module
correctly yet(there is no CXX_MODULE in our project).

Change-Id: I9a6a754e863b51b3e3a4b1eaf864ddab24e92f75
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>

Added some licenses and fixed some QT_BEGIN_LICENSE tags

Change-Id: I4077ccc9a3505c055c56dcb07da85e19523695b5
Reviewed-by: Frederik Gladhorn <frederik.gladhorn@digia.com>

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

These components provides a more powerful layout features necessary
for desktop applications.

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