[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Protux-design] Re: [Protux-devel] how to open PM?
From: |
Reinhard Amersberger |
Subject: |
Re: [Protux-design] Re: [Protux-devel] how to open PM? |
Date: |
Tue, 21 Jan 2003 11:06:40 +0100 |
address@hidden schrieb am 21.01.03 10:38:03:
>
> Luciano Giordana wrote:
>
> >The idea is cool. But I dont think we have to follow the initial caracter to
> >make this.
> >
> yes, that's an important point, similar actions have to stay around the
> same center key
>
But we have to pay attantion to keeping the jmb actions as
intuitive/self-explanatory as possible!
> >We could just use positional variations, such <FR> . <FE> , <FS> , <FX> or
> >any other similar stuff
> >
So I think this above is really hard to keep in mind.
> >Also, we have been using the term "Project Manager" more than File Stuff.
> >
Yes, you are right!
But here we have a problem, because 'P' is the center key for 'PAN' stuff, so
we should try to avoid confusing users!
So <P> or <<P>> should be used to open a 'Pan Properties' dialog to change the
value of the selected node in a dialog.
Maybe we should think about using another name for PM.
> >so, it could be <P1> <P2> <P3> <P4> , and so on to open diferent tabs
> >directly or
> >
> ><P0> to simple open the project manager and then type <1> <2> <3> ... inside
> >it to change the tabs...
> >
Yeah, I like this contextive behavior! :-)
> i really like that idea, but instead of <P0> just <P> to open the PM
> with the last viewed tab... <Pn> to open tab n, and <n> to switch to
> tab n... that's really good... of course <<P>> stays GlobalProperties...
>
> /Martin
Again the PAN problem.
But we could continue the old discussion thread started in jmb.map ?
# Settings stuff - CENTER KEY : Right_Control
"GLOBAL PROPERTIES" <<K>> 0 0 0x0050 0 #
<<P>> # could be <<SE>> ?
# "COMPONENT PROPERTIES" <K> 0 0 0x0050 0 #
<P> # could be <SE> ?
# LG : you were right Reinhard, next action conflicts with n..[P]. Now what !??
# RA : We could use 'SE' that should mean 'SEttings' ?
# This conflicts with 'SELECT ENVELOPES' stuff, but 'SELECT ENVELOPES' is
another story, because I think this
# should be a contextive action in the future.
# COMPONENT INFO [K] 0 0 0x0050 0 # [P]
# could be [SE] ?
RFC
Reinhard
______________________________________________________________________________
Mit der Gruppen-SMS von WEB.DE FreeMail erreichen Sie mit einem Klick
alle Freunde gleichzeitig! http://freemail.web.de/features/?mc=021180