Merge lp:~lukas-kde/unity8/newWindowDecosAndPanel into lp:unity8
| Status: | Superseded | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Proposed branch: | lp:~lukas-kde/unity8/newWindowDecosAndPanel | ||||||||||||
| Merge into: | lp:unity8 | ||||||||||||
| Prerequisite: | lp:~lukas-kde/unity8/activateWindows | ||||||||||||
| Diff against target: |
1983 lines (+723/-313) 24 files modified
qml/Components/PanelState/PanelState.qml (+3/-2) qml/Components/WindowControlButtons.qml (+76/-31) qml/Components/graphics/window-close.svg (+14/-0) qml/Components/graphics/window-maximize.svg (+12/-0) qml/Components/graphics/window-minimize.svg (+13/-0) qml/Panel/Handle.qml (+2/-2) qml/Panel/Indicators/client/IndicatorsClient.qml (+1/-1) qml/Panel/IndicatorsMenu.qml (+11/-2) qml/Panel/MenuContent.qml (+1/-1) qml/Panel/Panel.qml (+68/-80) qml/Panel/PanelBackground.qml (+0/-21) qml/Stages/ApplicationWindow.qml (+29/-3) qml/Stages/DecoratedWindow.qml (+24/-15) qml/Stages/DesktopStage.qml (+79/-55) qml/Stages/SessionContainer.qml (+25/-1) qml/Stages/SurfaceContainer.qml (+56/-4) qml/Stages/WindowDecoration.qml (+15/-10) qml/Stages/WindowResizeArea.qml (+66/-21) tests/mocks/Unity/Application/MirSurface.cpp (+52/-0) tests/mocks/Unity/Application/MirSurface.h (+16/-0) tests/qmltests/Panel/tst_Panel.qml (+45/-11) tests/qmltests/Stages/tst_DesktopStage.qml (+84/-31) tests/qmltests/Stages/tst_WindowResizeArea.qml (+31/-12) tests/qmltests/tst_Shell.qml (+0/-10) |
||||||||||||
| To merge this branch: | bzr merge lp:~lukas-kde/unity8/newWindowDecosAndPanel | ||||||||||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-11-20 | |
| Daniel d'Andrada (community) | 2015-11-05 | Approve on 2015-11-20 | |
|
Review via email:
|
|||
This proposal has been superseded by a proposal from 2015-11-23.
Commit Message
Implement new visuals for panel and window decorations
Description of the Change
Implement new visuals for panel and window decorations
* Are there any related MPs required for this MP to build/function as expected? Please list.
lp:~lukas-kde/unity8/activateWindows
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* Did you make sure that your branch does not contain spurious tags?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
Yes
* If you changed the UI, has there been a design review?
Yes
| Albert Astals Cid (aacid) wrote : | # |
| Lukáš Tinkl (lukas-kde) wrote : | # |
Conflicts resolved
| Daniel d'Andrada (dandrader) wrote : | # |
I think it's worth considering using pre-rendered images (PNGs) instead of rendering them at runtime from SVGs for performance reasons.
We keep the SVG, but also ship a couple or prerendered versions at common grid unit resolutions (like for 1080p monitors, etc). So if we don't have a PNG for the grid unit at hand, we fallback to rendering one at runtime from the original SVG.
And maybe that scheme could be turned into a component of its own.
| Daniel d'Andrada (dandrader) wrote : | # |
> I think it's worth considering using pre-rendered images (PNGs) instead of
> rendering them at runtime from SVGs for performance reasons.
>
> We keep the SVG, but also ship a couple or prerendered versions at common grid
> unit resolutions (like for 1080p monitors, etc). So if we don't have a PNG for
> the grid unit at hand, we fallback to rendering one at runtime from the
> original SVG.
>
> And maybe that scheme could be turned into a component of its own.
I recall this had a significant impact on start up time back in 2010/2011. Not sure how relevant it still is with todays hardware.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2034
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 2047. By Lukáš Tinkl on 2015-11-09
-
restoreFromMini
mized() -> restore()
restore() -> restoreFromMaximized()
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2046
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 2048. By Lukáš Tinkl on 2015-11-09
-
bring back the panel hiding/showing animations
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2047
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Lukáš Tinkl (lukas-kde) wrote : | # |
> > I think it's worth considering using pre-rendered images (PNGs) instead of
> > rendering them at runtime from SVGs for performance reasons.
> >
> > We keep the SVG, but also ship a couple or prerendered versions at common
> grid
> > unit resolutions (like for 1080p monitors, etc). So if we don't have a PNG
> for
> > the grid unit at hand, we fallback to rendering one at runtime from the
> > original SVG.
> >
> > And maybe that scheme could be turned into a component of its own.
>
> I recall this had a significant impact on start up time back in 2010/2011. Not
> sure how relevant it still is with todays hardware.
This doesn't seem to have any impact on performance, design would be fine with giving me whatever format assets we want I guess.
I feel like going with SVGs has the advantage of being able to freely resize the decoration once we allow clients to provide their own in the longterm.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2048
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild:
http://
| Daniel d'Andrada (dandrader) wrote : | # |
Could you please remove all those empty <g></g> from the SVGs?
| Daniel d'Andrada (dandrader) wrote : | # |
> This doesn't seem to have any impact on performance
Sure, as it's used only for a couple of small images. But it might if adoption becomes widespread throughout unity8, specially on phones. We can worry about it once we get there.
| Daniel d'Andrada (dandrader) wrote : | # |
Don't know how to reset it. "Abstain" will do it for now...
| Daniel d'Andrada (dandrader) wrote : | # |
- run "make tryDesktopStage"
- Launch camera-app, gallery-app and webbrowser-app
Why are those apps being launched fullscreen now?
| Daniel d'Andrada (dandrader) wrote : | # |
By the way, what about those rounded corner I saw in the design mock up. Should we have a trello card for it or was it dropped?
| Daniel d'Andrada (dandrader) wrote : | # |
Is qml/Stages/
| Daniel d'Andrada (dandrader) wrote : | # |
There's not a shadow around the indicators panel (that thing that you drag down from the top) anymore. Instead, there's just a black line on its left side. Is it how design intended?
| Daniel d'Andrada (dandrader) wrote : | # |
- run "make tryShell
- select desktop size
- select desktop usage scenario
- unlock the shell (dismiss lockscreen)
- Click on the indicators bar grey area between the focused app name and the indicators icons
This is what you get:
qml/Stages/
| Daniel d'Andrada (dandrader) wrote : | # |
I don't get why you set "hoverEnabled: true" on that MouseArea where you put WindowControlBu
| Daniel d'Andrada (dandrader) wrote : | # |
Still in Panel.qml:
"// TODO here would the LIM come"
What's "LIM"? Also the sentence doesn't look grammatically correct.
| Daniel d'Andrada (dandrader) wrote : | # |
Would it be too much to ask for adding a way to show/hide window controls and name in "make tryPanel" so we can see how it interacts with other panel components and states without having to run a fullblown Shell.qml test?
| Daniel d'Andrada (dandrader) wrote : | # |
qml/Panel/
If so, could you please nuke it? It's a pretty ridiculous component anyway... (a Rectangle with a pre-defined color)
- 2049. By Lukáš Tinkl on 2015-11-12
-
sanitize SVGs
| Lukáš Tinkl (lukas-kde) wrote : | # |
> Could you please remove all those empty <g></g> from the SVGs?
Done
| Lukáš Tinkl (lukas-kde) wrote : | # |
> - run "make tryDesktopStage"
> - Launch camera-app, gallery-app and webbrowser-app
>
> Why are those apps being launched fullscreen now?
Because of the bugfix for https:/
| Lukáš Tinkl (lukas-kde) wrote : | # |
> By the way, what about those rounded corner I saw in the design mock up.
> Should we have a trello card for it or was it dropped?
Right, we will need another task in trello for this (qtmir I suppose)
| Lukáš Tinkl (lukas-kde) wrote : | # |
> Is qml/Stages/
Yup, for the desktop spread imo
| Daniel d'Andrada (dandrader) wrote : | # |
In DesktopStage.qml:
Your updateForegroun
| Daniel d'Andrada (dandrader) wrote : | # |
> > - run "make tryDesktopStage"
> > - Launch camera-app, gallery-app and webbrowser-app
> >
> > Why are those apps being launched fullscreen now?
>
> Because of the bugfix for https:/
> /webbrowser-
Can you please stick to the purpose of this branch and just update the visuals?
Please put this bug fix in a separate merge proposal.
| Lukáš Tinkl (lukas-kde) wrote : | # |
> Still in Panel.qml:
>
> "// TODO here would the LIM come"
>
> What's "LIM"? Also the sentence doesn't look grammatically correct.
Locally integrated menus
| Lukáš Tinkl (lukas-kde) wrote : | # |
> I don't get why you set "hoverEnabled: true" on that MouseArea where you put
> WindowControlBu
Because the whole group is visible only on mouse over _and_ I need the individual mouse over visual effect when hovering over a single button. Any idea how to do that better?
| Daniel d'Andrada (dandrader) wrote : | # |
On 12/11/2015 11:04, Lukáš Tinkl wrote:
>> Still in Panel.qml:
>>
>> "// TODO here would the LIM come"
>>
>> What's "LIM"? Also the sentence doesn't look grammatically correct.
> Locally integrated menus
Please write it down in full. Acronyms just hamper communication.
- 2050. By Lukáš Tinkl on 2015-11-12
-
nuke unused component
| Lukáš Tinkl (lukas-kde) wrote : | # |
> qml/Panel/
> and didn't notice any difference. Also grepping for it didn't show anything.
>
> If so, could you please nuke it? It's a pretty ridiculous component anyway...
> (a Rectangle with a pre-defined color)
Yup, it's gone
| Lukáš Tinkl (lukas-kde) wrote : | # |
> In DesktopStage.qml:
>
> Your updateForegroun
> model once again unnecessarily. The delegates are already ordered according to
> ApplicationManager model, so their indexes match. No need to look up for it.
Not quite the same, the window might be maximized (its state) but not visually. In other words, the window might be maximized and minimized at the same time.
- 2051. By Lukáš Tinkl on 2015-11-12
-
remove acronyms
| Lukáš Tinkl (lukas-kde) wrote : | # |
> On 12/11/2015 11:04, Lukáš Tinkl wrote:
> >> Still in Panel.qml:
> >>
> >> "// TODO here would the LIM come"
> >>
> >> What's "LIM"? Also the sentence doesn't look grammatically correct.
> > Locally integrated menus
>
> Please write it down in full. Acronyms just hamper communication.
That's what the design docs use but yea, you're right
| Daniel d'Andrada (dandrader) wrote : | # |
On 12/11/2015 11:10, Lukáš Tinkl wrote:
>> In DesktopStage.qml:
>>
>> Your updateForegroun
>> model once again unnecessarily. The delegates are already ordered according to
>> ApplicationManager model, so their indexes match. No need to look up for it.
> Not quite the same, the window might be maximized (its state) but not visually. In other words, the window might be maximized and minimized at the same time.
Their state doesn't change their index.
appRepeater already iterates on ApplicationManager. I don't get how is
it possible to have a delegate in that repeater whose index differs from
the model it was created from.
- 2052. By Lukáš Tinkl on 2015-11-12
-
fix warning when clicking the panel with no maximized window at all
| Lukáš Tinkl (lukas-kde) wrote : | # |
> - run "make tryShell
> - select desktop size
> - select desktop usage scenario
> - unlock the shell (dismiss lockscreen)
> - Click on the indicators bar grey area between the focused app name and the
> indicators icons
>
> This is what you get:
> qml/Stages/
> null
Fixed
| Lukáš Tinkl (lukas-kde) wrote : | # |
> On 12/11/2015 11:10, Lukáš Tinkl wrote:
> >> In DesktopStage.qml:
> >>
> >> Your updateForegroun
> ApplicationManager
> >> model once again unnecessarily. The delegates are already ordered according
> to
> >> ApplicationManager model, so their indexes match. No need to look up for
> it.
> > Not quite the same, the window might be maximized (its state) but not
> visually. In other words, the window might be maximized and minimized at the
> same time.
>
> Their state doesn't change their index.
And that's problem, I need to know what index is the (visually) maximized window at. To be able to cast the panel drop shadow and focus the correct window when clicking on the panel.
> appRepeater already iterates on ApplicationManager. I don't get how is
> it possible to have a delegate in that repeater whose index differs from
> the model it was created from.
- 2053. By Lukáš Tinkl on 2015-11-12
-
readd the accidentally dropped indicators shadow
| Lukáš Tinkl (lukas-kde) wrote : | # |
> There's not a shadow around the indicators panel (that thing that you drag
> down from the top) anymore. Instead, there's just a black line on its left
> side. Is it how design intended?
Yup, I re-added it now but there's still the thin black line... dunno where it comes from :) Will investigate
- 2054. By Lukáš Tinkl on 2015-11-12
-
optimize the for loop
- 2055. By Lukáš Tinkl on 2015-11-12
-
remove the left black divider for now
| Lukáš Tinkl (lukas-kde) wrote : | # |
> > There's not a shadow around the indicators panel (that thing that you drag
> > down from the top) anymore. Instead, there's just a black line on its left
> > side. Is it how design intended?
>
> Yup, I re-added it now but there's still the thin black line... dunno where it
> comes from :) Will investigate
Should be fixed now
| Lukáš Tinkl (lukas-kde) wrote : | # |
> > On 12/11/2015 11:10, Lukáš Tinkl wrote:
> > >> In DesktopStage.qml:
> > >>
> > >> Your updateForegroun
> > ApplicationManager
> > >> model once again unnecessarily. The delegates are already ordered
> according
> > to
> > >> ApplicationManager model, so their indexes match. No need to look up for
> > it.
> > > Not quite the same, the window might be maximized (its state) but not
> > visually. In other words, the window might be maximized and minimized at the
> > same time.
> >
> > Their state doesn't change their index.
>
> And that's problem, I need to know what index is the (visually) maximized
> window at. To be able to cast the panel drop shadow and focus the correct
> window when clicking on the panel.
>
> > appRepeater already iterates on ApplicationManager. I don't get how is
> > it possible to have a delegate in that repeater whose index differs from
> > the model it was created from.
Optimized the for loop by returning the already available index from appManager
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2049
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 2056. By Lukáš Tinkl on 2015-11-12
-
add a checkbox to see window control buttons
| Lukáš Tinkl (lukas-kde) wrote : | # |
> Would it be too much to ask for adding a way to show/hide window controls and
> name in "make tryPanel" so we can see how it interacts with other panel
> components and states without having to run a fullblown Shell.qml test?
Done
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2055
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2056
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 2057. By Lukáš Tinkl on 2015-11-13
-
fix some failing tests
- 2058. By Lukáš Tinkl on 2015-11-13
-
more shell tests fixing
- 2059. By Lukáš Tinkl on 2015-11-13
-
wait for the shell rendering
- 2060. By Lukáš Tinkl on 2015-11-13
-
clear the window controls and title when showing the desktop spread
| Daniel d'Andrada (dandrader) wrote : | # |
> > Would it be too much to ask for adding a way to show/hide window controls
> and
> > name in "make tryPanel" so we can see how it interacts with other panel
> > components and states without having to run a fullblown Shell.qml test?
>
> Done
But I don't see the name of the application there when the mouse is not hovering over it.
| Daniel d'Andrada (dandrader) wrote : | # |
- make tryShell
- Select desktop size and desktop usage scenario
- Unlock screen
- Select phone size & usage scenario
- Unlock screen again
Expected outcome:
Indicators bar does not display the focused application name
Actual outcome:
Indicators bar displays the focused application name, like in a desktop usage scenario.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2057
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2060
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2057
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2057
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Lukáš Tinkl (lukas-kde) wrote : | # |
> > > Would it be too much to ask for adding a way to show/hide window controls
> > and
> > > name in "make tryPanel" so we can see how it interacts with other panel
> > > components and states without having to run a fullblown Shell.qml test?
> >
> > Done
>
> But I don't see the name of the application there when the mouse is not
> hovering over it.
I don't see any applications in "make tryPanel", what should it show then?
- 2061. By Lukáš Tinkl on 2015-11-18
-
properly destroy PanelState
in order not to leave artifacts behind (window title, controls, etc)
| Lukáš Tinkl (lukas-kde) wrote : | # |
> - make tryShell
> - Select desktop size and desktop usage scenario
> - Unlock screen
> - Select phone size & usage scenario
> - Unlock screen again
>
> Expected outcome:
> Indicators bar does not display the focused application name
>
> Actual outcome:
> Indicators bar displays the focused application name, like in a desktop usage
> scenario.
Thanks for spotting, fixed
- 2062. By Lukáš Tinkl on 2015-11-18
-
add an option to show a fake window title in panel
| Lukáš Tinkl (lukas-kde) wrote : | # |
> > > Would it be too much to ask for adding a way to show/hide window controls
> > and
> > > name in "make tryPanel" so we can see how it interacts with other panel
> > > components and states without having to run a fullblown Shell.qml test?
> >
> > Done
>
> But I don't see the name of the application there when the mouse is not
> hovering over it.
Ok, added an option to show a fake window title
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2061
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2062
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Daniel d'Andrada (dandrader) wrote : | # |
- Run "make tryShell"
- Select desktop size and usage scenario
- Unlock the screen
- Launch a fullscreen app, like gallery
Expected outcome:
The applications takes the entire area of Shell.qml
Actual outcome:
It doesn't take the space on top that was previously occupied by the indicators bar.
Comments:
I know you said it works when run for real on a laptop/device. But those manual tests should reproduce exactly what happens "for real". Otherwise it undermines the value of qml tests. There's no reason why they should behave differently. This is just high-level QML code afterall.
- 2063. By Lukáš Tinkl on 2015-11-20
-
merge trunk
- 2064. By Lukáš Tinkl on 2015-11-20
-
fix for fullscreen apps not taking the panel height into account
| Lukáš Tinkl (lukas-kde) wrote : | # |
> - Run "make tryShell"
> - Select desktop size and usage scenario
> - Unlock the screen
> - Launch a fullscreen app, like gallery
>
> Expected outcome:
> The applications takes the entire area of Shell.qml
>
> Actual outcome:
> It doesn't take the space on top that was previously occupied by the
> indicators bar.
>
> Comments:
> I know you said it works when run for real on a laptop/device. But those
> manual tests should reproduce exactly what happens "for real". Otherwise it
> undermines the value of qml tests. There's no reason why they should behave
> differently. This is just high-level QML code afterall.
Fixed
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2063
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2064
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Daniel d'Andrada (dandrader) wrote : | # |
In test_tappingOnD
Please keep launching 3 applications. It's important that neither the "from" nor the "to" applications are focused before the test. That's why a 3rd one is being launched.
I guess the problem is that camera-app is now fullscreen in DesktopStage. So just replace it with another an application that is not fullscreen, like gmail-webapp.
You will have to change its saved mock geometry so that it doesn't overlap unity8-dash or dialer-app.
So just replace camera-app and gallery-app below with other two non-fullscreen apps:
"""
}
"""
I suggest gmail-webapp and twitter-webapp
| Daniel d'Andrada (dandrader) wrote : | # |
Likewise in test_tappingOnW
| Daniel d'Andrada (dandrader) wrote : | # |
In test_maximisedA
"""
findChild(
"""
You should click on the maximize button instead of directly calling an internal function. We should strive to keep code paths as close to real usage as possible.
"""
var dialerApp = startApplicatio
"""
I guess you're using dialer-app here because it starts in normal state (ie non-maximed and non-fullscreen). If so, please explicitly check for this condition in the test to have it clear.
- 2065. By Lukáš Tinkl on 2015-11-20
-
merge trunk
- 2066. By Lukáš Tinkl on 2015-11-20
-
fix bad merge
- 2067. By Lukáš Tinkl on 2015-11-20
-
amend the test to launch 3 apps and maximize the windows by clicking the button
| Lukáš Tinkl (lukas-kde) wrote : | # |
Tests now launch 3 apps and use the maximize button manually
| Daniel d'Andrada (dandrader) wrote : | # |
In test_maximizeAp
I think you should s/camera-
| Daniel d'Andrada (dandrader) wrote : | # |
Likewise in test_applicatio
s/camera-
s/gallery-
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2065
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 2068. By Lukáš Tinkl on 2015-11-20
-
don't change expectations for maximized apps (that are also fullscreen)
| Lukáš Tinkl (lukas-kde) wrote : | # |
> In test_maximizeAp
>
> I think you should s/camera-
> code expectations
Fixed
| Lukáš Tinkl (lukas-kde) wrote : | # |
> Likewise in test_applicatio
>
> s/camera-
> s/gallery-
I don't see a problem with this testcase
| Daniel d'Andrada (dandrader) wrote : | # |
test_applicatio
In this test you launch gallery-app and click on its maximize button.
But I cannot do it manually because gallery-app starts in fullscreen. No maximize button in sight. That's why I told you to change it into an app that doesn't start in fullscreen.
- 2069. By Lukáš Tinkl on 2015-11-20
-
s/gallery/gmail
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2067
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 2070. By Lukáš Tinkl on 2015-11-21
-
merge trunk
- 2071. By Lukáš Tinkl on 2015-11-23
-
merge prereq and fix conflicts
- 2072. By Lukáš Tinkl on 2015-11-23
-
don't set width/height directly
- 2073. By Lukáš Tinkl on 2015-11-23
-
don't hide the decoration when the window is not visible
- 2074. By Lukáš Tinkl on 2015-11-25
-
get rid of the dp(2) gap for the orange line
- 2075. By Lukáš Tinkl on 2015-11-25
-
#333333 -> #292929
- 2076. By Lukáš Tinkl on 2015-11-25
-
get rid of the orange line in the handle
- 2077. By Lukáš Tinkl on 2015-11-25
-
Light font weight for the root indicator labels

Text conflict in qml/Components/ WindowControlBu ttons.qml DecoratedWindow .qml DesktopStage. qml Stages/ tst_DesktopStag e.qml
Text conflict in qml/Panel/Panel.qml
Text conflict in qml/Stages/
Text conflict in qml/Stages/
Text conflict in tests/qmltests/
5 conflicts encountered.