D16937: Make Kickoff separators leaner (less opaque) and narrower (the length of a highlighted menu item)

[Root]

rooty added a comment.


  In D16937#361182 <https://phabricator.kde.org/D16937#361182>, @ngraham wrote:
  
  > I could get behind reducing the opacity. Perhaps to 0.7 or 0.6. Removing the frame for the scroll area to get rid of the extra lines on the top or bottom when it's scrollable could also make sense now that these lines are a part of the design. But I'll need a bit of convincing to agree to making the lines have different widths.
  
  
  0.6 sounds good - it makes them stick out but not too much.
  F6429369: image.png <https://phabricator.kde.org/F6429369>
  
  I'm not so sure myself anymore. Don't get me wrong, it looks fine when both the separators are of equal length and lowered opacity, but in that case they make the transition from header to item list a lot less gradual / smooth (//too much of a good thing//). This also makes the scroll bar come unusually close to the upper separator. Also, the lines won't ever actually be of equal length with the tab bar on the left/right in either configuration: F6429373: image.png <https://phabricator.kde.org/F6429373>
  
  > Stepping back, the goal was to separate the three distinct elements from one another so that they actually look like three distinct elements. I wanted to move away from the "everything merges into everything else" look and towards a look that says "this is a structured thing with a header and a tab bar and a content area".
  
  This provides for both the partition/disconnect and the unity that Kickoff needs, without being too intrusive on either front.
  
  > To a certain extent, this goal was compromised because I couldn't get the lines to touch the actual edge (any ideas how to do that, #plasma <https://phabricator.kde.org/tag/plasma/> folks?).
  
  I wouldn't recommend this though, it'd still do well to look like a single widget.
  
  > But I feel like reducing the line length takes us in the opposite direction by making the header and the content view seem like a part of the same thing, with a superfluous line between them. The obvious next question is, "why do we need that line, can't we get rid of it?" and then we're back to where we started. All of this stems from not being confident enough in Kickoff's visual identity to confidently separate things IMHO.
  > 
  > Am I making any sense here?
  
  What you're saying does make sense, but I'd hardly call the line superfluous (it provides for much needed structure). And the header and content view are in fact part of the same thing, the widget - except that this way they become **discrete**, working in tandem. That's why I said the separator idea was a good in the first place.

REPOSITORY
  R119 Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D16937

To: rooty, ngraham, #vdg
Cc: romangg, filipf, plasma-devel, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20181117/fa195261/attachment-0001.html>