On 08/22/2011 12:39 PM, hannes.janet...@gmail.com wrote: > On Mon, Aug 22, 2011 at 12:11 PM, Brian 'morlenxus' Miculcy > <morlen...@gmx.net> 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 So, you think common people go to the window menu to change the maximize state? I would guess that they use the window button for that... > 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. Things don't get faster if you just put them to the toplevel as the eye of the users need to read all the available options if there is no logic behind it. Also i don't think people are glad now that the stacking menu is on top level. I think most would be more glad if you can easily stack a window on top instead of having to go to the submenu with a lot of often unused options. > >> 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. Should have ask. > >> 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' Yes, but before there where useful shortcuts to common options (see below). > 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. Yes, that can't decided alone, that's why there was a discussion on the ml about this. > >> 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. Again, 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 > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
------------------------------------------------------------------------------ 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
