| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
Conflicts:
src/declarative/QmlChanges.txt
|
| | | |
|
| | | |
|
| | |\
| | | |
| | | |
| | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | | |
|
| | | | |
|
| | |\ \
| | | | |
| | | | |
| | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
WebView: idealWidth -> preferredWidth (as per QSizePolicy)
WebView: idealHeight -> preferredHeight
WebView: status -> statusText
WebView: mouseX -> clickX (parameter to onDoubleClick)
WebView: mouseY -> clickY (parameter to onDoubleClick)
WebView: cacheSize -> pixelCacheSize (may later go away)
WebView: lost "interactive" property (always true now)
|
| | | | | |
|
| |_|_|/
|/| | | |
|
|\ \ \ \
| |/ / /
| | | |
| | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Flicks could stop at some odd places if the viewport size changed
during flicking. We now attempt to adjust to the correct behaviour
at the ends of the viewport.
|
| |/ / /
|/| | | |
|
| |_|/
|/| |
| | |
| | |
| | | |
This logic needs to be centralized, so that all the various model classes
handle the same set of data sources.
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
Conflicts:
src/declarative/qml/qmlengine.cpp
|
| |\ \
| | | |
| | | |
| | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | |\ \
| | | | |
| | | | |
| | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | |\ \
| | | | | |
| | | | | |
| | | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Allows you to write things like "geometry: Qt.rect(0,0,100,100)" and
"color: Qt.hsla(.7,.5,.2)"
|
| | | |\ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | | | | | |
|
| | | |_|/ /
| | |/| | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Using TitleBar in twitter too, this slight change prevents a copy of the
whole component.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Only openUrl() currently.
Reviewed-by:Aaron Kennedy
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This reverts commit f51450571addf2cb9a55153b209b8c1a45898193.
We apparently do not want to either make the id easily accessible or
have a special case the turns things into strings. And the autotests
are all broken anyways - fixing something only they use isn't important
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | | | | |
|
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | | |
This is the first step to allowing QML to interact with REST style
APIs in the same way as a webbrowser can.
|
|\ \ \ \ \
| |/ / / /
| | | | |
| | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | |/ /
| |/| |
| | | |
| | | |
| | | | |
Changing this check to engine() checks both if the engine() exists
and if the parent context exists.
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
Conflicts:
src/declarative/extra/qmlbehavior.cpp
src/declarative/extra/qmlbehavior.h
|
| | | |
| | | |
| | | |
| | | |
| | | | |
I messed up when I reapplied this patch to the branch head.
This also adds an extra test for the case fixed.
|
| |\ \ \
| | |/ /
| | | |
| | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | |\ \
| | | | |
| | | | |
| | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | |\ \
| | | | | |
| | | | | |
| | | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | |\ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
Conflicts:
doc/src/declarative/anchor-layout.qdoc
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
1st step in animation class heirarchy redesign.
|
| | | |\ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | | | | | | |
|
| | | |_|_|/ /
| | |/| | | | |
|
| | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Focus Scopes are an additional focus paradigm, designed to be more
suitable for use by declarative UI.
With focus scopes, graphics view continues to have a single focused item -
this is the single item to which key events are *actually* delivered. To
simplify the description that follows, we will say that this element has
"global focus".
Focus scopes partitions focus into a heirarchy. Each focus scope may have one
sub-focused item, which may itself be another focus scope. The sub-focused item
is said to be have "scope focus" or its ancestor focus scope. Consequently,
any given QGraphicsItem may be globally focused, scope focused (which means it
is focused within its ancestor focus scope) or both.
A focus scope corresponds to a QGraphicsItem with the ItemIsFocusScope flag set.
As graphics view doesn't have a single root item, a "virtual" focus scope is
modeled as being the ancestor of all the root items.
With focus scopes, when QGraphicsItem::setFocus() is called, the item's
ancestors are searched until a focus scope is found (remembering the "virtual"
root focus scope is used if there is no *actual* ancestor scope). The item is
set as the sub-focused item of the focus scope (becoming focus scoped) and any
existing sub-focused item of that focus scope has scope focus removed from it.
The item that receives global focus is found by beginning at the "virtual"
root focus scope and recursively decending into each item that is scope focused
until a leaf (non-focus scope) item is reached. The implementation takes
shortcuts here to be slightly more optimal, but the end result should be the
same as though this abstract algorithm was evaluated each time.
Two manual examples of focus scope are found under examples/declarative/focusscope
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
declarative/demos
|
| | | | | | |
|
|\ \ \ \ \ \
| | |/ / / /
| |/| | | |
| | | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| |/ / / / |
|