The point of the convention was that related properties should be part
of the same "block" or "group" of assignments, which can be achieved by
ensuring that they are directly above/below one another. Bunching up
assignments onto one line for a few properties should not be a
recommended practice.
Change-Id: Ie84163b3261e7138d69678e059a91c2c82b43507
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
The concensus to use semicolons for blocks of code was reached on the
mailing list:
http://lists.qt-project.org/pipermail/development/2016-October/027441.html
Change-Id: I98ce87c623c189bdfac8cfac5c0fa80e5a831c18
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
Reviewed-by: Robin Burchell <robin.burchell@viroteck.net>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: Topi Reiniö <topi.reinio@theqtcompany.com>
Qt copyrights are now in The Qt Company, so we could update the source
code headers accordingly. In the same go we should also fix the links to
point to qt.io.
Change-Id: Iedecec76f88fcf709d31bf7bfc5fe817302ecae1
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
It doesn't make sense to advocate the use of QtQuick 2.0 anymore. We
can expect that people target Qt 5.3 in the Qt 5.3 documentation ...
Change-Id: I6ac8dca59a2717fe6d8baec13d968bd74070e90e
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
-ported from qtdeclarative.git
-fixed snippet and image paths to doc/snippets and doc/images
Because this guide will need to cover more than Qt QML and Qt Quick,
this guide does not need to be in qtdeclarative.
Change-Id: Id6a47420a1e73b5c55b7233571557e3558e82043
Reviewed-by: Sze Howe Koh <szehowe.koh@gmail.com>
Reviewed-by: Geir Vattekar <geir.vattekar@digia.com>
Mitch Curtis
Antti Kokko
Kai Koehne
Jerome Pasion