rooty added a comment.

  > No, it's not.
  
  Yeah it is :D
  
  > Trivial options have a lot of cost attached to them: They make a UI noisier 
and more intimidating, and therefore less appealing. They also make it less 
effective by making it harder to find what you're looking for, as you have to 
scan through more options. They also introduce additional codepath and states, 
increasing the maintenance burden and complicating user support ("is your 
configuration X or Y?").
  
  And that's why :D Your argument hinges on the idea that something trivial 
makes the UI cluttered (and also imposes a maintenance burden). I think that's 
too broad/dogmatic and can be true but it really doesn't have to be the case. 
The task manager settings aren't really laden with settings so this would 
hardly be an imposition.
  
  Plasma's incredibly tweakable. I like to think that's one of the reasons 
people like it so much.
  But if you're gonna force the issue, I'd much rather keep the feature and 
remove the option to disable it.
  
  > Moreoever, adding options like this is almost always lazy and unloading a 
burden on the user instead of designing a UI that does the right thing and 
doesn't need the option.
  >  Options have to be earned.
  
  Lazy? No.
  A UI that wouldn't require you to pick an option might be a better choice.
  A UI that wouldn't require you to pick an option but would still allow you to 
do so might be the best choice.
  
  > My take is this:
  > 
  > - If the danger of users clicking the indicator accidentally and getting 
upset by it is high, this is a bad feature and shouldn't go in.
  
  Agreed.
  
  > - If the danger isn't actually that high, there's no need for an option.
  
  Agree to disagree.
  
  > A possible improvement to make here is to make the indicator visually react 
to hover by recoloring the icon, to teach that it's seperately interactive and 
will do something different than clicking elsewhere on the task button, so 
users get habituated not to click it accidentally. This should probably be done 
anyway (we're usally pretty triggerhappy on the hover feedback).
  
  This would be nice to have, I agree. This might also be a good thing to 
implement in Latte, @mvourlakos thoughts?
  
  > No, if that bug report comes and comes repeatedly, we know it's a bad 
feature and drop it again.
  
  While a potential consideration, it's not certain that the feature should be 
removed in case this happens. It would be silly for us to, say, stop shipping 
the notification widget just because there we get bug reports about glitchy 
placement, for example.
  
  > According to the linked discussion, Chrome is nuking the entire feature - 
it's not about the indicator being clickable. And they're doing it for 
unrelated reasons that are mostly strategic to the web platform and don't 
concern us here.
  
  They GNOME'd it. :D

REPOSITORY
  R119 Plasma Desktop

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

To: faridb, #plasma, #vdg, ngraham, filipf, hein
Cc: rooty, hein, filipf, mvourlakos, ngraham, broulik, plasma-devel, jraleigh, 
GB_2, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, 
sebas, apol, mart

Reply via email to