On Sun, 27 Dec 2009 11:10:43 +1030 Samuel Nicholas <nicholas.sam...@gmail.com> said:
> Hi, > > I was thinking of having a go at re-working some of the messy > configuration dialogues because it seems a really simple task, and i > have had a few thought i would like to threw out there. you'd be my hero if you did! :) > in the pager dialogue there are some options that seem more logical to > be provided by the input configuration dialogue like: absolutely! a lot of the config dialog options are based entirely on what the code does, not on what is logical to a person. the dialog should be there to make such config abstracted and logical to a human who isnt writing the code. :) > ----General Settings---- > Flip desktop on mouse wheel > drag and drop button > drag whole desktop button > > So my questions are > what is e's policy on config dialogues that provide input binding > options, instead of (or aswell as) the input config dialogue? > should the dialogue create & delete the binding itself? like keybindings? > should it provide just an on/off switch for the binding that is > configured in the input module? > should it not present these option at all, leaving it to the input module? well there is no input module - you mean the input config dialogs (key bindings, mouse bindings, edge bindings etc.) ? as such i'd say "do whatever is best", BUT make sure you dont break other things. so that means - you can add/delete and change existing key and mouse bindings, but... do it so it WORKS. that means u can edit them separately and your config dialog that modifies these wont get confused, and also so it wont kill other bindings the user set up not related to the ones you auto-added/deleted/modified > My dreaming mind tells me it would be great to have an input config > widget to embed in the advanced section, exposing only the input > bindings for that module. well this is where some of it you want to mvoe to e itself - make it a shared utility/routine. specifically what you want is the thing that captures key and/or modifiers - the rest you dont really need except for "any modifier" as a checkbox. (well also displaying the key name + modifier used). so maybe just these need to go into e itself and then everything can use them. > Cheers, > Samuel > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
