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.
in the pager dialogue there are some options that seem more logical to be provided by the input configuration dialogue like: ----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? 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? 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. 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
