[Pidgin] #4986: automatic chat input field resizing should be optional, regression from 2.3
Pidgin
trac at pidgin.im
Tue Mar 4 15:22:59 EST 2008
#4986: automatic chat input field resizing should be optional, regression from 2.3
---------------------------+------------------------------------------------
Reporter: swbrown | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: pidgin (gtk) | Version: 2.4.0
Resolution: | Keywords: chat input resize
Pending: 0 |
---------------------------+------------------------------------------------
Comment (by jason0x21):
Replying to [comment:49 deryni]:
> jason0x21: The gain from our removing the manual resize ability was the
fact that the automatic resizing could work with significantly less
problems, problems that people were complaining about. There is nothing
wrong with the desire to want to do that, but desire based on nothing is a
poor reason to complicate and support extra code, especially if the
current mechanism can be made to suit. Why do you arbitrarily resize the
input area? Are there times you need to do that specifically? Or do you
just like to do it because you can?
So removing manual resizing makes automatic resizing work better? Or were
there problems specific to manual resizing (and only manual resizing?).
Because I've said before: make automatic a default, with an option to
return to manual only. It's pretty clear there aren't any people who want
both at once.
I don't feel like I need a reason other than "This is the way it worked
before, and I really liked it." That's why they're called "preferences"
after all. This is IM, and nobody's doing mission-critical work with IM.
Likewise, the developers don't need a reason to add functionality. We're
all happy to try new functionality. However, when stuff is _removed_,
there needs to be a clear reason why it simply can't be made to work
anymore.
It should be obvious to most of the devs now that people are clamoring for
manual resize back, and no amount of "you need to provide a use case" is
going to shut them up. It's because they're not wrong to want it back.
In fact, demanding a use case for a preference is kind of rude (can anyone
really justify why they need "bold" fonts?) I know that many of the
messages were harsh in the beginning, but I'd wager that most people who
saw it went first to the preferences pane to try and make it work the old
way (I know I did).
--
Ticket URL: <http://developer.pidgin.im/ticket/4986#comment:50>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list