Re: [Geany-devel] editor context menu - Re: Search submenu for editor popup menu
May be make sense create context menu like in jEdit (context menu in jEdit is editable)? Is really good jEdit feature, and would be very nice if Geany have this feature too. -- WBR, Denis Koryavov. ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] editor context menu - Re: Search submenu for editor popup menu
On Thu, 16 Sep 2010 09:54:09 +1000 Lex Trotman ele...@gmail.com wrote: 2. let the user pick say four most used top level commands since we are *never* going to agree on them. Use a simplified version of the customise toolbar dialog. Personally I don't think it's worth doing this. Put the most useful things at toplevel, everything else in submenus. Ah but whats the most useful? Things which are useful for the largest number of users. There is also an issue of letting new users discover some useful things easily that they might not know Geany does. I *never* use insert comments from the popup and rarely from the menu (changelog mostly) so for me having any insert comments in the popup is a waste of space. Which is why a single Insert submenu would be better. I'm not suggesting its required, but if someone out there has the time to implement it this would remove all the disagreements :-) Is it so bad to solve the disagreements using submenus? This avoids maintenance and code complexity of popup configurability, which I predict isn't going to be pretty. C is not a good GUI language. 3. pack the rest in submenus. format format submenu as now What about Commands - at least half of these are context related. insert insert submenu including the insert comments I think at least me and Enrico use insert comments a lot, we'd like it to be toplevel. The other insert items could maybe be in a submenu (also insert alt whitespace). This would be like having Go to Tag Definition in toplevel but Go to Tag Declaration in a submenu as it's less common. And I of course use the tool differently so I don't want any inserts Did you see my Insert submenu reply? and use go to declaration much more than go to definition due to the language I use most :-). Correct me if wrong, but Go to declaration is only needed for function prototypes and extern declarations, no? The feature is only useful for C/C++, not for most users. So having to find it in the proposed popup Search submenu is acceptable, no? For all user names : [insert name here] uses it differently again so almost no one is fully happy with a fixed menu. As mentioned above, I'm not trying to force my preferences on anyone. I'm trying to find a good default that is reasonable (but not ideal) for everyone. Regards, Nick ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] editor context menu - Re: Search submenu for editor popup menu
On Thu, Sep 16, 2010 at 13:57, Nick Treleaven nick.trelea...@btinternet.com wrote: On Thu, 16 Sep 2010 09:54:09 +1000 Lex Trotman ele...@gmail.com wrote: 2. let the user pick say four most used top level commands since we are *never* going to agree on them. Use a simplified version of the customise toolbar dialog. Personally I don't think it's worth doing this. Put the most useful things at toplevel, everything else in submenus. Ah but whats the most useful? Things which are useful for the largest number of users. There is also an issue of letting new users discover some useful things easily that they might not know Geany does. I *never* use insert comments from the popup and rarely from the menu (changelog mostly) so for me having any insert comments in the popup is a waste of space. Which is why a single Insert submenu would be better. I'm not suggesting its required, but if someone out there has the time to implement it this would remove all the disagreements :-) Is it so bad to solve the disagreements using submenus? This avoids maintenance and code complexity of popup configurability, which I predict isn't going to be pretty. C is not a good GUI language. Where I really see an advantage of having the context menu customisable are plugin actions. With my gproject plugin and my not-publicly-released ctags plugin I also added several items at the top of the context menu (plus separators). I can imagine that if several plugins do a similar thing, the context menu gets pretty messy (someone will put the new items to the top, someone to the bottom, someone will use separators, someone not, ...) Also the menu starts growing even if the user doesn't really use the context menu item of the given plugin. This is why I really like the Lex's idea of having a fixed set of items in the menu that are always present (possibly containing submenus) and a variable set of configurable items. If the configurable items can be arbitrary items from the keybindings list, the plugins won't have to add their own items into the context menu and the user can only pick those he wishes to be present. It's not necessary to have submenus in the customisable part of the menu - a plain list of items would be fine. By default the variable list could also contain the questionable entries that someone wishes to be present in the menu and someone not. Those who don't want to have them can just remove them if they wish. Of course this would require some work... Jiri ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] editor context menu - Re: Search submenu for editor popup menu
On 16 September 2010 21:57, Nick Treleaven nick.trelea...@btinternet.com wrote: On Thu, 16 Sep 2010 09:54:09 +1000 Lex Trotman ele...@gmail.com wrote: 2. let the user pick say four most used top level commands since we are *never* going to agree on them. Use a simplified version of the customise toolbar dialog. Personally I don't think it's worth doing this. Put the most useful things at toplevel, everything else in submenus. Ah but whats the most useful? Things which are useful for the largest number of users. A pessimistic interpretation of this is: If its not C we're not interested :-) There is also an issue of letting new users discover some useful things easily that they might not know Geany does. Discovery should be in the main menus that are always visible, not in popups which are hidden. I *never* use insert comments from the popup and rarely from the menu (changelog mostly) so for me having any insert comments in the popup is a waste of space. Which is why a single Insert submenu would be better. Yes, erm I thought thats what I proposed and below you were proposing to also have insert(s) in the top level, my misunderstanding. I'm not suggesting its required, but if someone out there has the time to implement it this would remove all the disagreements :-) Is it so bad to solve the disagreements using submenus? It doesn't solve which commands go in the top level of the popup for greatest convenience, which was the only bit I was suggesting as configurable. This avoids maintenance and code complexity of popup configurability, which I predict isn't going to be pretty. C is not a good GUI language. Too true, so make it manually edited configuration for now. 3. pack the rest in submenus. format format submenu as now What about Commands - at least half of these are context related. insert insert submenu including the insert comments I think at least me and Enrico use insert comments a lot, we'd like it to be toplevel. The other insert items could maybe be in a submenu (also insert alt whitespace). This would be like having Go to Tag Definition in toplevel but Go to Tag Declaration in a submenu as it's less common. And I of course use the tool differently so I don't want any inserts Did you see my Insert submenu reply? As I said above, I read this as implying you also wanted insert item(s) in the toplevel, not just in the submenu. and use go to declaration much more than go to definition due to the language I use most :-). Correct me if wrong, but Go to declaration is only needed for function prototypes and extern declarations, no? For C, for C++ the function declaration is part of the class declaration and is separate from the definition. The class declaration has more information and is used much more often than the prototype/extern declaration is in C. The feature is only useful for C/C++, not for most users. So having to find it in the proposed popup Search submenu is acceptable, no? Well, if goto definition is in the top level then I'd say no :-) it needs to be the other way round for C++ users. And I would have thought that there were other languages that made the distinction between declarations and definitions, not just C/C++. For all user names : [insert name here] uses it differently again so almost no one is fully happy with a fixed menu. As mentioned above, I'm not trying to force my preferences on anyone. I'm trying to find a good default that is reasonable (but not ideal) for everyone. And I'm trying to suggest that it would be better for users to be able to pick their own ideal. It may be that no one who is interested has enough time to implement it, even without a GUI, but if we don't ask we won't get :-). Once at least some configuration is available then things like Jiri's suggestion become possible as further extensions. Cheers Lex Regards, Nick ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] editor context menu - Re: Search submenu for editor popup menu
On Wed, 15 Sep 2010 11:15:23 +1000 Lex Trotman ele...@gmail.com wrote: As noted in another response, IAW Gnome HIG right click popups S/B context related things. What does S/B mean? FWIW I'd: 1. remove undo/redo/select all as they are not context related Then are common editor popup menu commands though - gedit and Scite have them. nedit has undo/redo and mousepad has select all. I'm not particularly opposed to removing them, just mentioning that some users will expect to see them there. 2. let the user pick say four most used top level commands since we are *never* going to agree on them. Use a simplified version of the customise toolbar dialog. Personally I don't think it's worth doing this. Put the most useful things at toplevel, everything else in submenus. 3. pack the rest in submenus. format format submenu as now What about Commands - at least half of these are context related. insert insert submenu including the insert comments I think at least me and Enrico use insert comments a lot, we'd like it to be toplevel. The other insert items could maybe be in a submenu (also insert alt whitespace). This would be like having Go to Tag Definition in toplevel but Go to Tag Declaration in a submenu as it's less common. search find items and as you say search selected goto open file, goto line etc Personally I would combine search and goto, that way we can share a GtkMenu widget between the search menu and popup menu. This is a good strategy because we don't have to maintain two separate menus if most items are needed in each. Regards, Nick ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] editor context menu - Re: Search submenu for editor popup menu
Hey Nick, On 16 September 2010 00:33, Nick Treleaven nick.trelea...@btinternet.com wrote: On Wed, 15 Sep 2010 11:15:23 +1000 Lex Trotman ele...@gmail.com wrote: As noted in another response, IAW Gnome HIG right click popups S/B context related things. What does S/B mean? Sorry should be I was in a hurry so more acronyms than usual. FWIW I'd: 1. remove undo/redo/select all as they are not context related Then are common editor popup menu commands though - gedit and Scite have them. nedit has undo/redo and mousepad has select all. I'm not particularly opposed to removing them, just mentioning that some users will expect to see them there. Ok, well lets see what others think. 2. let the user pick say four most used top level commands since we are *never* going to agree on them. Use a simplified version of the customise toolbar dialog. Personally I don't think it's worth doing this. Put the most useful things at toplevel, everything else in submenus. Ah but whats the most useful? I *never* use insert comments from the popup and rarely from the menu (changelog mostly) so for me having any insert comments in the popup is a waste of space. I'm not suggesting its required, but if someone out there has the time to implement it this would remove all the disagreements :-) 3. pack the rest in submenus. format format submenu as now What about Commands - at least half of these are context related. insert insert submenu including the insert comments I think at least me and Enrico use insert comments a lot, we'd like it to be toplevel. The other insert items could maybe be in a submenu (also insert alt whitespace). This would be like having Go to Tag Definition in toplevel but Go to Tag Declaration in a submenu as it's less common. And I of course use the tool differently so I don't want any inserts and use go to declaration much more than go to definition due to the language I use most :-). For all user names : [insert name here] uses it differently again so almost no one is fully happy with a fixed menu. search find items and as you say search selected goto open file, goto line etc Personally I would combine search and goto, that way we can share a GtkMenu widget between the search menu and popup menu. This is a good strategy because we don't have to maintain two separate menus if most items are needed in each. Good idea. Cheers Lex Regards, Nick ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel ___ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
