On Fri, Dec 17, 2010 at 9:16 PM, Peter Hosey <bore...@adium.im> wrote: > On Dec 17, 2010, at 13:46:24, Michael Schade wrote: > If it truly is a Service, then I say not: It is better for it to remain a > Service and be available in all applications than for it to become something > Adium-specific. > > I would suggest giving it a keyboard shortcut, though, so that people can do > a quick ⇧⌘⇠/⌃⌘A (assuming you choose ⌃⌘A as your keyboard shortcut) to invoke > Accentuate with the minimum of effort. I haven't looked to see whether you've > done this, so my apologies if you have. >
Good point. I did start working on an actual OS X service, although that was a parent project that led to developing the implementation of the API in AccentuateUs.m. There are a few problems with going the Service route that implementing in an application-specific way would fix: - A less technical aspect, but shipping it with Adium would bring it to the user so that more are aware and can use it to communicate well. - It would allow people to have their text automatically accentuated when they press return, rather than having to select all of the text, use the keyboard shortcut, and then send the message, which would be tedious if you typed often - The Services menu cannot be dynamically populated, so we are unable to send updated lists of languages and would have to hard code them all. Overall, the Service route is nice for a backup, but poorer in execution, primarily for the second point: the large inconvenience of needing to accentuate on every message being sent. Best, Michael
