Guest User


a guest
Sep 16th, 2011
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.99 KB | None | 0 0
  1. <aday> elleuca, is this a serious comment? >
  2. <bebot> Bug 659045: normal, Normal, ---, richard, UNCONFIRMED, Please add back lid action configuration
  3. <aday> i honestly can't tell
  4. <andre_> unlikely
  5. <aday> <humour> tags could be useful :)
  6. or <joke>, maybe
  7. <hadess> aday, the ":D" at the end kind of gives it away...
  8. <aday> hadess, i couldn't work out if he was trying to be serious as well as funny
  9. <elleuca> aday, it was serious, as well as office-runner is a serious solution to "I wanna know what my own computer does when I close the lid and I don't wanna be power user" :P (<humor>)
  10. <aday> elleuca, just checking :)
  11. <elleuca> aday, anyway that change is something I would like in upstream, it's simple, unobtrusive and gives the idea "developers pay attention to users needs and accept their request without breaking the original design"; IMHO you need this message if you want people will trust changes occurred with 3.x serie (and the ones that will come)
  12. <hadess> elleuca, we don't expose every single setting we have in the UI, and that one won't be an exception
  13. hadess halfline
  14. <elleuca> hadess, am I saying to expose all settings?
  15. <hadess> elleuca, except that 1) having it in the control-center is a bad way of doing it 2) it doesn't solve the actual use case
  16. hadess halfline
  17. <aday> elleuca, my view is that what users need is for suspend/resume to work
  18. <aday> they don't need a setting
  19. <hadess> elleuca, you're using it as an excuse of why we should show the settings in the UI
  20. hadess halfline
  21. <elleuca> hadess, sorry?
  22. <hadess> you're saying "I want to know what my computer will do because i changed that setting"
  23. hadess halfline
  24. it's a hidden setting, and just like every other hidden setting, it's not shown in the UI
  25. <aday> elleuca, i fully agree that we need to show that we care about users. i just don't think we need to sacrifice the user experience in order to do that
  26. <aday> it's a different bug ;)
  27. <elleuca> hadess, no, I'm saying "I want to know why my computer gone to suspend and I didn't asked for it"
  28. <hadess> elleuca, you closed the lid, that's what it does when you close the lid
  29. hadess halfline
  30. <hadess> and i'll add again that adding back the preference in the control center is a crappy way of helping the use cases that were mentioned in the bug report
  31. <elleuca> hadess, the subsequent objection is: "why should I've to install power tools or learn how to use gsettings command line utility in order to make my own hardware acting in the way I want?" (and please note I'm able to use gsettings...)
  32. <aday> elleuca, you shouldn't have to
  33. <hadess> elleuca, why should you even care what it does when you close the lid?
  34. <hadess> everybody uses it to suspend
  35. <elleuca> is this a serious reply?
  36. <hadess> and if we showed "suspend" we would get complaints that it doesn't suspend when you have an external display plugged in
  37. yes, it's a serious reply
  38. <elleuca> here in Italy about 60% of people vote Berlusconi; should I do it too?
  39. <steph> +1
  40. <hadess> if that's the way you want the conversation to go, just stop talking right now
  41. i'm not interested
  42. <elleuca> good to know, but I hope GNOME people will not blame Ubuntu for that downstream change to Power panel, Martin just tried to make it more suited to ubuntu users needs
  43. <hadess> bullshit
  44. if he considered the users needs, he wouldn't be adding it back to the power panel
  45. <hadess> i seriously doubt that any designer had an input into his patch to revert to a 2.32 UI
  46. <aday> elleuca, users needs != what a very small number of users say they want
  47. <hadess> aday, and there's always a difference between what users say they want, and what they're actually trying to achieve
  48. <elleuca> aday, I'm sure about it, but I prefer to relax and listen them from time to time
  49. <aday> elleuca, who isn't listening?
  50. <hadess> elleuca, read the bug again then, and see the use cases
  51. <hadess> actually, "use case", singular
  52. "i'm moving the laptop from one end to the other, and don't want it to suspend"
  53. <elleuca> hadess, do you prefer a separate bug for "I want to know what my hardware will do and I like to change if it doens't match what I like"?
  54. <hadess> elleuca, yeah, because i can close it as wontfix already
  55. <elleuca> great
  56. I'll do
  57. <aday> elleuca, do you consider that to be good design?
  58. <elleuca> aday, do you mean the patch from martin or let people know what happens on lid close?
  59. <hadess> "letting people know what happens on lid close"?
  60. it suspends
  61. like windows and osx do
  62. <aday> elleuca, > "I want to know what my hardware will do and I like to change if it doens't match what I like"
  63. <elleuca> aday, honestly yes (me and at least other 3 people using GNOME 3 on laptop)
  64. (while I'm not sure I can label it as "good _design_", more "good behavoir")
  65. <aday> elleuca, do you realise that that goes against the design approach of pretty much all modern devices?
  66. <aday> (following it as a general rule, i mean)
  67. <elleuca> aday, if modern devices are tablets and smartphones, no I didn't; they simply turn off the screen -- and no lid to close :) -- if modern devices are hmm... macbooks? ... I don't know; i never had the ability to test them about suspend behavior
  68. <hadess> laptops for the past ~15 years
  69. <aday> elleuca, i think it's important to differentiate between what you personally want and what is good for gnome
  70. <elleuca> aday, I never said I want it, you know I can use other tools to check and change those setting, please don't put in this way, it's not a personal request
  71. <hadess> and *why* do they want to see what it would do?
  72. by default it suspends
  73. the only way it wouldn't suspend is if they changed it
  74. which means they would likely know how to see what it's set to after changing it
  75. <aday> elleuca, fair enough. my point is that these decisions are designed to make gnome competitive
  76. <elleuca> however, I quit by now, I've to go back to work and it seems me and you are just repeating ourself, see you later :)
  77. <aday> see you :)
  78. <hadess> sure we are, but then again, so are you
  79. so there you go
Add Comment
Please, Sign In to add comment