[Pidgin] #5419: Input field is not resizable
Pidgin
trac at pidgin.im
Thu Apr 3 13:14:19 EDT 2008
#5419: Input field is not resizable
---------------------------+------------------------------------------------
Reporter: megaloman | Owner:
Type: defect | Status: closed
Priority: minor | Milestone:
Component: pidgin (gtk) | Version: 2.4.0
Resolution: duplicate | Keywords: usability
Pending: 0 |
---------------------------+------------------------------------------------
Comment (by megaloman):
You're changing my words other way round. I said that I prefer to have
flexible input field - that's a reason - can you see a word "flexible"??
auto growing input field is not flexible, but it's noisy and annoying for
many users. Also I like space - that's why I bought a laptopq equipped
with 15.4 inch LCD screen and resolution of 1680x1050 pixels.
Others gave you a good reasons too: they use pidgin to exchange code or
they like to write longer messages - auto growing window does not work for
them either. But developers are denying that and they just changing max
input field size from 4 to 8 lines. Do you really think, it will calm
people and make them happy? I bet, it won't.
I do understand, that managing many options in the program, it's a pain
and increases workload. But at this point developers should be flexible
too - for a major issues like that there should be an option in the
pidgin, not as a plugin.
I've posted a feature request for that plugin to be included in pidgin and
you know what? they refused to included, but they said "feel free to
create a package" - I don't even know how to create package nor how to
apply patch an build a plugin!
And why poeple creating forks? Guess! Because they are not happy with
developers' decisions. Now I am being forced to use fork, because actually
fork works like I expect application to work.
Coming back to the issue - I've even suggested improvement of current
behaviour - to include min lines and max lines settings - I could set it
up to the same value (ie. 4) and I would be happy. But that suggestion was
ignored. Instead I got auto growing from 2 to 8 - for me that change does
nothing. And that suggestion is not a big deal - instead of having hard
coded number, user can decide what he wants - is it that hard and cost
effective?
going further:
why do pidgin give an option to have tabs on top or on the bottom of the
window? it increases complexity! let's force users to have tabs fixed on
the bottom/top/whatever.
why do have an option "Hide new IM conversation"? let's force all
conversation to pop up on top! less complexity!
and what about formatting? let's make it plain text always - less
complexity!
and why on the "Conversation" tab Default Formatting shows input field of
5 lines height, not two? inconsistency! shocking behaviour!
Do you get my point? I bet you don't.
Have you read my example? Gnome by default brows through folders in their
controversial "spatial" mode - some users don't like it. Instead of
forcing people to use their not desired solution, or saying to them "do a
plugin / use a fork / go and fuck yourself" they did an option to browse
windows in a browser mode. Everyone is happy.
As some one pointed that out - developers are not keen on listening to
users. You're turning our words to "I don't like it", you just don't
understand that's a major usability problem.
But I give you other ideas:
make conversation window fixed size - users should not be allowed to
change windows size, as you, developers, know better what the size should
be - right?
don't allow users to switch off sounds - users should have a sound
notifications and should hear all this noisy sounds, it makes them
happier! they might not like it, but they will get used to. They will get
used to - it does not mean they will ever see any good sides of your
choices.
Shame on you guys.
--
Ticket URL: <http://developer.pidgin.im/ticket/5419#comment:8>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list