This reverts commit 894ade6f1e2767a8866642a4ea278659730c26d8
Storing the search text was not thought well through. It causes bad user experience.
Also, the real solution for showing filtered Example sets in the chooser is coming here: https://codereview.qt-project.org/#change,82906
Change-Id: Ibb51bf5c0fa08fdeb8530a19d823ba97a3c167d1
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
in QtCreator.ini under "WelcomePage/ExamplesSearchString".
The installer pre-set that setting, and in that way pre-
select a set of examples.
Change-Id: I8ac5a38ad0bd3f33875ef1997ccbf0352410dcc3
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
That makes it more visible, which is especially important when we show
example sets that do not come from a Qt version there.
Change-Id: Ib99955e70abb95053d9e8cd718ab599153e6eaaf
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
Added with setting "Help/InstalledExamples" which is a string list, each
string is a triple of (display name, manifest parse path, examples
path), joined with '|'.
If a documentationPath for a Qt version is already added through the
InstalledExamples setting, we do not show an extra combo box item for
it. That makes it possible for an installer to register a single example
set for the same Qt version in different variants (e.g. iOS, Android
x86, Android arm)
Change-Id: I42dd8f9ca9cb6cee247e3dc8ce9d014e56852e79
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
This is a somewhat different solution for improving the
performance of the welcome screen. It has the added benefit
of caching loaded items while still retaining a decent
performance.
Change-Id: I9927a90f1b7de5bb06c43b16dc80cb2afec3f8ad
Reviewed-by: Ulf Hermann <ulf.hermann@digia.com>
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
By tying the scroll offsets and visible areas of the two scrollable
elements together we avoid excessive loading times for the examples.
Change-Id: I6522ef3e6c0454e5bb05bef143953d8d1850ffdc
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
We only need one scrollable element in the WelcomePage. By passing
the height properties of inner elements to the outermost one we can
avoid multiple vertical scrollbars next to each other. Since this
removes the QScrollArea around the welcome page it fixes
QTCREATORBUG-10796
Task-number: QTCREATORBUG-10796
Change-Id: I08b0409e21f16be6c3e0e5a58f2665320d0a14fe
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
This ports the welcome screen to use QtQuick 2.0.
I have disabled the plugin on Qt4 builds.
Change-Id: Ia921d0747c8f7d4441c88fc9fb77b822496091f4
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Expand the width from 140 to 200 px to make sure that usual names do
fit.
Change-Id: I311ba32a7f300e96ec6b6d183d1078467a71e26a
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Somehow AbstractItemModel is not registered in Qt 4.
So we cannot use the qtVersionModel as a property.
Change-Id: Iac822998cb660d317e2b750dde9f3207c66f5feb
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
I kept the limitation to 3024 pixels to keep the patch small
and avoid accidents/regressions.
Task-number: QTCREATORBUG-8411
Change-Id: I1e2fc453500358d67bdb62732adcdc8e7fa17e1b
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
Instead of placing the "complete" GridView to a ScrollArea we now add
a ScrollBar to the GridView. This means that only visible delegates are
instanciated and the GridView gets alot faster.
Change-Id: I63b8593b260acd4d3a786a99c7dd58507c12e221
Reviewed-by: Alessandro Portale <alessandro.portale@nokia.com>
Major visual upgrade and refactoring.
I also added dummydata and a qmlproject file.
Change-Id: I5ebc6dfb4718a37bb20766669272b85bc9316316
Reviewed-on: http://codereview.qt-project.org/5708
Reviewed-by: hjk <qthjk@ovi.com>
