unity-2d

Merge lp://qastaging/~sladen/unity-2d/unity-2d-no-glow-lp933578 into lp://qastaging/unity-2d

unity-2d-no-glow-lp933578
Merge into trunk

Proposed by Paul Sladen on 2012-02-24

Status:

Superseded

Proposed branch:

lp://qastaging/~sladen/unity-2d/unity-2d-no-glow-lp933578

Merge into:

lp://qastaging/unity-2d

Diff against target:

174 lines (+2/-65) (has conflicts)

8 files modified

shell/common/SearchEntry.qml (+0/-10)
shell/common/artwork/desktop_dash_background.sci (+2/-2)
shell/dash/CategoryHeader.qml (+0/-22)
shell/dash/LensButton.qml (+0/-8)
shell/dash/LensView.qml (+0/-1)
shell/dash/MultiRangeButton.qml (+0/-7)
shell/dash/Star.qml (+0/-7)
shell/dash/TickBox.qml (+0/-8)

Contents conflict in shell/launcher/artwork/launcher_pip_ltr.png

To merge this branch:

bzr merge lp://qastaging/~sladen/unity-2d/unity-2d-no-glow-lp933578

Undecided

Fix Released

Link a bug report

Reviewer	Date Requested	Status
Paul Sladen (community)		Needs Resubmitting on 2012-02-24
Michał Sawicz	2012-02-24	Pending
Gerry Boland	2012-02-24	Pending
Review via email: mp+94585@code.qastaging.launchpad.net

This proposal supersedes a proposal from 2012-02-24.

This proposal has been superseded by a proposal from 2012-02-24.

Description of the change

No Glow assets + fixups for (LP: #933578)
This includes replacements assets for:
  Pips + arrows
  Dash search box and search box status icons
  Dash edge background (transparent)
  Dash edge background (non-transparent)
With associated code changes:
  Removal of blurRadius except for background itself
  Background tiling phase realignment for transparent background

Revision history for this message

Michał Sawicz (saviq) wrote on 2012-02-24: Posted in a previous version of this proposal

Just removing "blurRadius" from DropShadows means the shadow will actually be there, and drawn, just that it won't blur. So you end up with a (expensive) copy of the text behind it.

Please completely remove the whole "effect: DropShadow {...}" properties to actually get rid of the shadows.

review: Needs Fixing

Revision history for this message

Michał Sawicz (saviq) wrote on 2012-02-24: Posted in a previous version of this proposal

Please also provide a before and after images for design sign-off.

review: Needs Fixing

Revision history for this message

Michał Sawicz (saviq) wrote on 2012-02-24: Posted in a previous version of this proposal

We need a way to indicate focus on the "Filter results", it was only being highlighted with the glow, now it's too easy to get "lost" in the dash when keyboard-navigating.

We have a similar issue with category headers that don't have "expand" links, so consistency here would probably make sense (not "it's broken" consistency, but a way to indicate focus on them).

review: Needs Fixing

Revision history for this message

Paul Sladen (sladen) wrote on 2012-02-24: Posted in a previous version of this proposal

I believe in all of these locations hover/focus is indicated by colour:white && blurRadius. The colour: white is still there and continues to provide the primary highlight.

There is a design solution for replacing the white highlight with a full-width background grey highlight, and this is in Unity 3D. However, Gerry requested that the merge say on focus and be a minimal diff without other changes other than removing the glow from the assets and code.

Revision history for this message

Paul Sladen (sladen) wrote on 2012-02-24: Posted in a previous version of this proposal

Before, After, and Delta screenshots attached to parent bug report.

review: Needs Resubmitting

Revision history for this message

Michał Sawicz (saviq) wrote on 2012-02-24: Posted in a previous version of this proposal

> I believe in all of these locations hover/focus is indicated by colour:white
> && blurRadius. The colour: white is still there and continues to provide the
> primary highlight.

> There is a design solution for replacing the white highlight with a full-width
> background grey highlight, and this is in Unity 3D.

Except that the label I mentioned ("Filter results") is already white, so we lose
focus indication completely. Please leave that one instance of the glow in place,
we'll fix the whole approach to focus in dash in a separate MR.

> However, Gerry requested that the merge say on focus and be a minimal diff
> without other changes other than removing the glow from the assets and code.

That's ok, but just removing the blurRadius property doesn't make sense. The whole
"effect: DropShadow { ... }" component is responsible for just the glow, so to remove
the glow we need to remove the whole of it.

lp://qastaging/~sladen/unity-2d/unity-2d-no-glow-lp933578 updated on 2012-02-24

940. By Paul Sladen on 2012-02-24: Glow: Temporaily glow/blur on "Filter Results" button to provide state constrast
per https://code.launchpad.net/~sladen/unity-2d/unity-2d-no-glow-lp933578/+merge/94560/comments/204013
941. By Paul Sladen on 2012-02-24: Drop DropShadow and associate /* HACK */ per
https://code.launchpad.net/~sladen/unity-2d/unity-2d-no-glow-lp933578/+merge/94560/comments/204013

Revision history for this message

Paul Sladen (sladen) wrote on 2012-02-24:

Done on both accounts.

review: Needs Resubmitting

lp://qastaging/~sladen/unity-2d/unity-2d-no-glow-lp933578 updated on 2012-02-27

942. By Paul Sladen on 2012-02-24: Additionally remove the second "Ugly Hack" message per Saviq
although it is unclear where the associate hack is/was
943. By Paul Sladen on 2012-02-24: Self-revert; LensView: restore the separate namespace "moving" usage
944. By Paul Sladen on 2012-02-27: Merge to HEAD; manually resolve binary merge conflict:
shell/launcher/artwork/launcher_pip_ltr.png
945. By Paul Sladen on 2012-02-27: Restore property moving && associated workaround warnings