(Much like Windows Messengers' Ctrl+Enter)
Enter Button
Option+Return is the Mac OS X standard. A future release (.8) will include support for Shift+Enter and Shift+Return (both keys exist on a Mac) [this is already finished in SVN]
Try my software!
#define ADIUMX pimp //by me
#define QUESTION ((2b) || (!2b))
Have you hugged a programmer today?
#define ADIUMX pimp //by me
#define QUESTION ((2b) || (!2b))
Have you hugged a programmer today?
-
wunderwood
- Crema
- Posts: 303
- Joined: Tue Dec 07, 2004 11:46 pm
- Location: Los Angeles, Cali, US
- Contact:
Yes, because the argument has shifted to one of (supposed) accessibility, not choosing the target to send to.
Try my software!
#define ADIUMX pimp //by me
#define QUESTION ((2b) || (!2b))
Have you hugged a programmer today?
#define ADIUMX pimp //by me
#define QUESTION ((2b) || (!2b))
Have you hugged a programmer today?
I didn't know about the Messages toolbar button. A toolbar button that sent messages would be great.
Here are some objective facts:
1. Messages can be created without using the keyboard (e.g. by dragging text into a message client window).
2. Without a send button, a user must use the keyboard to send a message.
3. It takes physical effort to move a hand between a normal keyboard and a normal mouse or trackball device.
4. Some muscle disorders affect large muscles more severely than small muscles. Extremity function can be near normal while arm and shoulder movement can be severely degraded.
Since I can't point to any research on the computer use of individuals with such disabilities, the next part of my argument is subjective. That is, although I can use the keyboard and the trackball pretty well, the physical effort it takes to switch between input devices is significant enough to affect my behavior. I have no idea of the number of users who have a similar experience, but I imagine it is very small percentage of users. But, a send button allows sending dragged text messages without switching input devices.
I also haven't asked the city to put in sidewalks on every street in every neighborhood. If I only ask for a sidewalk on my street, that doesn't make it any less of an accessibility issue. Although, you could say it's just a convenience to not have go through parking lots, over curbs and gravel on the side of the road in a wheelchair.
Or perhaps you were asking because of your concern for other users who like to use other clients. That is a good idea. When I have some more time and energy, perhaps I'll do that.
I am not aware of any studies on the matter, so I can't say that it fits into the objective Accessibility category as above. However, I don't think that my argument is purely subjective.bgannin wrote:Distinction:
1) Personal preference/justification - defined by your opinion, environment, and challenges... subjective is the key here
2) Accessibility - defined by observation and metrics and established principles and research... objective is the key here
I've not yet made my mind up on whether I feel it is a justified accessibility point, but I am pondering. The distinction I keep raising is that you are arguing for an objective point using entirely subjective facts and reasoning.
Here are some objective facts:
1. Messages can be created without using the keyboard (e.g. by dragging text into a message client window).
2. Without a send button, a user must use the keyboard to send a message.
3. It takes physical effort to move a hand between a normal keyboard and a normal mouse or trackball device.
4. Some muscle disorders affect large muscles more severely than small muscles. Extremity function can be near normal while arm and shoulder movement can be severely degraded.
Since I can't point to any research on the computer use of individuals with such disabilities, the next part of my argument is subjective. That is, although I can use the keyboard and the trackball pretty well, the physical effort it takes to switch between input devices is significant enough to affect my behavior. I have no idea of the number of users who have a similar experience, but I imagine it is very small percentage of users. But, a send button allows sending dragged text messages without switching input devices.
I don't think every accessibility feature is universally useful to every user with a challenge. Some accessibility features, such as curb cuts are almost universally helpful for accessibility, while other things, such as braille numbers on elevators are useful only to a subset of people. A send button option would make Adium more accessible to a small subset of users.bgannin wrote:I respect the fact that you yourself are in a situation requiring accessibility considerations and that you are sharing what you feel will better aid your in accessing your computer, I'm just not convinced it's an argument that applies for increasing overall accessibility for every user with a challenge of some form.
No, I have not addressed this with any other developers. I bring it up here because of my personal preference for using Adium. AIM has a send button, but I prefer Adium for other reasons.bgannin wrote:If it is a widespread issue - do you address this with developers of other IM clients (AIM, Proteus, iChat, Fire, et.all) that do support this so that all users requiring accessibility have support and choice, or just this client in this debate so you no longer have the inconvenience?
I also haven't asked the city to put in sidewalks on every street in every neighborhood. If I only ask for a sidewalk on my street, that doesn't make it any less of an accessibility issue. Although, you could say it's just a convenience to not have go through parking lots, over curbs and gravel on the side of the road in a wheelchair.
Or perhaps you were asking because of your concern for other users who like to use other clients. That is a good idea. When I have some more time and energy, perhaps I'll do that.