[Psi-devel] recent Remote Control, Execute Command, AdHoc work

[Norman Rasmussen]

On 26/06/05, Trejkaz <trejkaz at trypticon.org> wrote:
> Nah, the command itself is type "command-node".  The parent is type
> "command-list".  But both are in category "automation".
I haven't looked into this in depth, yet.  I have just fixed another
adhoc bug, so this investigation is pretty much next.  (It was going
to be first until the bug got me)

> The other thing Psi can do is refuse to run commands which advertise features
> that Psi doesn't support.  Although, most commands will advertise
> jabber:x:data and nothing more... unless a client pops up somewhere which
> uses commands for something really unique.
> 
This is tricky, because you can't really advertise features per
command as a can-have vs must-have.  Some features will enhance the
command, and some are required.

> Well, realistically I need to use the mouse to get to the roster and then get
> to the item in the roster, so left-clicking and then moving back to the
> keyboard would actually be slower than right-clicking and selecting the menu
> item directly. :-)
> 
You have two hands, right?  Actually this shortcut only works for
right-handed people.

On 26/06/05, Trejkaz <trejkaz at trypticon.org> wrote:
> Besides, disabling menu items is "considered harmful" in itself.  When a menu
> option is greyed out, the user has no idea why it's greyed out, so they can't
> even figure out how to use it.  I remember reading a paper on that subject,
> which asked designers to make all options actionable, but to pop up an
> informative dialog to describe exactly why the action couldn't be performed
> at the time it was requested.
> 
If you can't grey items, as a power user this would piss me off no
end.  If you make greyed out items clickable, that would be okay.

-- 
- Norman Rasmussen
 - Email: norman at rasmussen.co.za
 - Home page: http://norman.rasmussen.co.za/