On Mar 23, 2006, at 12:16 PM, Anselm R. Garbe wrote:
> On Thu, Mar 23, 2006 at 12:11:41PM -0500, John Nowak wrote:
>> On Mar 23, 2006, at 12:03 PM, John Nowak wrote:
>>
>>> On Mar 23, 2006, at 9:43 AM, Anselm R. Garbe wrote:
>>>
>>> I feel this is a great way of ending up at the same point (fast
>>> keyboard interaction) while making the learning curve much less
>>> steep (you can use everything perfectly fine without knowing any
>>> key commands initially, it is just a bit slower).
>>
>> While we're at it... Is there any way of building something like this
>> into wmii? For example, I'd like to be able to hold a key combination
>> and have that show me all of the key combinations in the program.
>> This way, all I actually have to remember is that one key command. I
>> use wmii every third day or so currently (doing a lot of development
>> in OS X at the moment, mainly because I'm in love with BBEdit/
>> TextWrangler), and each time I go back I find myself struggling to
>> remember the key commands. I'll get it eventually, but it might be
>> nice for new users to only have to remember "hold meta-? for help".
>> I'm not advocating menus or toolbars or anything here -- Just a
>> simple way of showing the key commands, perhaps greying out those
>> that are not available for the current situation (such as if no frame
>> is selected or if there is no other column to move to).
>
> That is conceptually not possible, because wmiirc decides what
> todo on a specific key press and wmiiwm does not know any
> semantic of shortcuts (except the move/resize shortcuts).
wmiiwm can't say to wmiirc "give me the list of shortcuts", and then
wmiiwm could just show them on the screen? Surely communication is
two-way, no? Forgive me if I'm lost here.
- John
Received on Thu Mar 23 2006 - 18:27:36 UTC
This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 16:01:33 UTC