[Bug 154535] ability to remove zoom in/out tool like any other applet
Craig Duquette
cduquette at gmail.com
Tue Jun 24 01:08:43 CEST 2008
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=154535
------- Additional Comments From cduquette gmail com 2008-06-24 01:08 -------
I've been following this discussion since the beginning and have heard promises that the cashew was going to be a huge transformation. I understand there's a vision behind this, but there hasn't been any discussion on what it is. If a user has a feature request generally you add the feature OR explain to them why this isn't a good idea.
Telling users for the past seven months you don't have time to discuss this issue and to wait is not the way to approach the problem. It's such a small feature request too, that has a huge visual impact on the user's screen. The rest of the desktop can be moved around and configured, but the cashew remains unconfigurable, featureless and fixed in place.
You make the argument that there are going to be great things coming for it, but why would you include a feature that's work in progress for a stable branch? Kwin has had their compiz like effects disabled by default for a while, not because they’re super unstable, but they’re not ready. People can opt-in to test them, but it’s not forced upon them. You’re doing the exact opposite, by displaying something that isn’t ready and forcing the users to adopt it. You create resentment for the feature and even if the cashew manages to cure world hunger people aren’t going to want to use it because they’re disgusted with it.
Let people disable it easily and when the time comes for this feature to mature they should want to use this feature. Features don’t become successful by shipping them useless and incomplete and telling users to wait until they’re coded. It’s like having a button on an application that when clicked displays a message box saying “coming soon.” That button shouldn’t be there. I’ve offered in the past to help get features in there, but you never given any direction toward what this cashew is going to be doing. Create a blog post discussing your intentions for the cashew, let people work on it and get people interested in the thing. Or if you've explained this thing, link us to some written dialog on the matter.
More information about the Panel-devel
mailing list