From: Cedric B. <ced...@fr...> - 2011-08-22 11:30:59
|
On Mon, Aug 22, 2011 at 12:39 PM, han...@gm... <han...@go...> wrote: > On Mon, Aug 22, 2011 at 12:11 PM, Brian 'morlenxus' Miculcy > <mor...@gm...> wrote: >> I don't like it, and i don't think it's an improvement: >> > Problem with the menu before was that there were 3 submenu levels to > get to common window options like maximize. Now all window options are > only 1 level away. The task of a window menu imho is not to present a > hierarchical ontology of window actions but to let the user reach > those actions quickly. > >> The old menu was sorted logically, easy to understand and clean: >> - Icon Options >> - Window Options >> - Some often used shortcuts (Move to, Always on Top, Sticky) >> - Close Button >> >> Now you have >> - Icon Options >> - Stacking >> - Maximize >> - Move to >> - Window >> - Settings >> - Close >> >> We are now back with a settings menu option, and the options in it are >> something like >> skip window list (which is an option) while we have a top level window >> submenu where are also options. > > I was not sure about the use of skip, I would think it's more > something one would use for per window class and should be remembered > automatically. > can be moved to window. > >> >> Also the shortcut options where liked by people, just a few days ago >> someone in #e told raster that he liked the fact that the sticky option >> is in the toplevel menu. Yes, this option can be readded, but then the >> toplevel window menu is back getting huge again. Yes, having a small >> toplevel menu was an idea of the old menu. >> > Before top-level had 6 entries now it is 7. 'sticky' or 'move to' > I've never used so what should be considered a good shortcut cannot be > decided for everyone. It would be good to have a configuration for > this though. I definitively agree with you on that. If we could at least choose what the first level of the menu will contain, that would be really great. I personally use this menu, only for moving window to another desktop or sticky it. For the rest I have keyboard shortcut so I almost never use it for maximise, nor fullscreen. But that may not be the case for a first time user nor for every one. So yes, being able to configure the first level and have all the rest in a submenu, would be really nice. >> I don't like how you just commit your stuff, not taking care of other >> peoples code. You commit and write something about "open for critique", >> but i think you should first ask people before you change everything >> just as you like. Start a discussion on ml, e.g. common things. >> >> Same with the efm_nav module. It allowed the user to enter a path in the >> efm toolbar with the keyboard. You removed the module from svn, i told >> you that it worked and that users might want it, but you didn't care and >> didn't restore. >> >> This is not my idea of working in a team on a project. If i follow your >> way, i would just commit the old menu code and overwrite your changes. >> >> Please revert. >> >> Brian 'morlenxus' Miculcy >> >> > > ------------------------------------------------------------------------------ > uberSVN's rich system and user administration capabilities and model > configuration take the hassle out of deploying and managing Subversion and > the tools developers use with it. Learn more about uberSVN and get a free > download at: http://p.sf.net/sfu/wandisco-dev2dev > _______________________________________________ > enlightenment-devel mailing list > enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > -- Cedric BAIL |