Don, since these changes that you announce probably require a lot of work on the localization files, may I ask that the localization template English.xml be published as early as possible. Ideally, a preview version of the template could be published in the translation forum, so the translators have a chance to get their job done before the new build is published.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know if your solution would help, but I'd very much like to tailor some of the menus, folding some groups of items n cascading menus. The Edit and View menus take all the screen height when viewed in 800x600, which makes in quite inconvenient to switch from a menu to another when the leftmost ones are involved.
Also some lists, like the Localization one in Preferences, display funny for the same reason. Problem vanishes at higher resolutions, but so does my ability to read the items :(
CChris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm 'old fashioned'. I much prefer standard menus over tabs.
I support Chris's call for a re-arrangement of menus. Length is a problem, but so is logical clustering. The solution to both is a full review of the menu contents.
I also support Thell's call for cascading menus for plugins. TextFX menus are far too long and would benefit from cascading menus. The smaller plugins (command-wise) would also benefit from cascading menus as they could use logical clustering when they needed it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here's my thoughts on rationalising the NP++ menus. It's a draft proposal which aims to increase the efficiency of the menus and efficacy by:
(a) reducing the number of menus (and therefore choice when looking for something)
(b) reducing the number of items on menus particularly Edit, the longest (and therefore assisting those using lower resolution screens and reducing choice when looking for something)
(c) clustering similar functions (so there are fewer places to look for something)
As I said, it's an early draft. As a consequence it may have typos and omissions. (The red underling is Word's spell checker.) It's a big change but some parts could be adopted and applied in small chunks as you see fit. It contains all the current functionality although you might not recognize it at first because I've changed some of the command names and concepts. For example, 'Syntax Format' replaces 'User Defined Languages' and 'Languages'. I've mostly brough similar things together but in a few cases, Run and Macros, I've split the functionality up.
There's a few areas where I don't know as much as I should. I've taken a punt with these. They are 'Run' which I've changed 'Commands' and ...
At the last minute I realised I've mis-used the ellipses mark (..) on menus. I decided to get this out rather than delay publication any longer. I'll add proper cascading menu marks, tick-marks for alternatives, and ticks for 'On' status if there are requests for a further iteration of this proposal.
I've also put myself in the firing line of plugin developers for daring to suggest uniform naming conventions in the Plugin menu, although this need not affect their program names.
> (a) reducing the number of menus (and therefore choice when looking for something)
IMO, all the sub menu are needed.
> (b) reducing the number of items on menus particularly Edit,
> the longest (and therefore assisting those using lower
> resolution screens and reducing choice when looking for something)
(Almost) All the Notepad++ features are listed in the menu to help users to learn them. So it's important to not remove commands from the menu.
> (c) clustering similar functions (so there are fewer places to look for something)
That's the solution to make menu shorter and cleaner.
In the next release, the sub-menu Edit/View and Languages are improved - these 3 menu will be cleaner and shorter. User can access to every single menu command even under a 640x480 display.
Don
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm just not sure how much development it takes to get those menus working. Your picture looks like the way HTML-Kit displays items.
In a nutshell, this may work right on Win 2K/XP/Vista, but if N++ is supposed to run under Win9x/ME then it may not be a good idea.
CChris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry, Greg, but I'd be mostly with Don about your proposal.
The only point where I might agree with removing some stuff regards the Format menu. To me, it seems that the current encoding format is something that doesn't change often, so its functionality could be moved to a new tab of the Preferences dialog.
Adding to the c) item:
Some TextFX submenus are quite lengthy, so I'd appreciate seeing them shortened using inner submenus. Convert and Viz are obvious candidates, and Edit might benefit as well.
Another option would be for long menus to split into mandatory and nonmandatiry items. Mandatory items would be displayed regardless. Non mandatory items would be displayed according to individual yes/no specific UI settings, configurable on the fly from Preferences, and all on by default. That way, users can clean menus the way they like better, and new users wouln't miss a single command. Of course it would be tedious to implement...
CChris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think that manipulate menus like horizontal tabs, it is much easier
Software
WPF C# Ribbon menus Control Library
http://www.codeproject.com/KB/WPF/ribboncontrol.aspx
Download free WPF ribbon control (Windows Scenic and Office 2007 - 2010, windows7_2009 style, too)
http://www.uxpassion.com/2008/11/download-free-wpf-ribbon-windows-scenic-office-2007-style/
http://en.wikipedia.org/wiki/Ribbon_\(computing)
wordpad2009
http://www.webtechpoint.com/wp-content/uploads/2008/12/wordpad20091.png
Don, since these changes that you announce probably require a lot of work on the localization files, may I ask that the localization template English.xml be published as early as possible. Ideally, a preview version of the template could be published in the translation forum, so the translators have a chance to get their job done before the new build is published.
I don't know if your solution would help, but I'd very much like to tailor some of the menus, folding some groups of items n cascading menus. The Edit and View menus take all the screen height when viewed in 800x600, which makes in quite inconvenient to switch from a menu to another when the leftmost ones are involved.
Also some lists, like the Localization one in Preferences, display funny for the same reason. Problem vanishes at higher resolutions, but so does my ability to read the items :(
CChris
> ...I'd very much like to tailor some of the menus, folding some groups of items n cascading menus.
I'll consider it.
Don
++ cascading menus for plugins.
I'm 'old fashioned'. I much prefer standard menus over tabs.
I support Chris's call for a re-arrangement of menus. Length is a problem, but so is logical clustering. The solution to both is a full review of the menu contents.
I also support Thell's call for cascading menus for plugins. TextFX menus are far too long and would benefit from cascading menus. The smaller plugins (command-wise) would also benefit from cascading menus as they could use logical clustering when they needed it.
Don,
Here's my thoughts on rationalising the NP++ menus. It's a draft proposal which aims to increase the efficiency of the menus and efficacy by:
(a) reducing the number of menus (and therefore choice when looking for something)
(b) reducing the number of items on menus particularly Edit, the longest (and therefore assisting those using lower resolution screens and reducing choice when looking for something)
(c) clustering similar functions (so there are fewer places to look for something)
As I said, it's an early draft. As a consequence it may have typos and omissions. (The red underling is Word's spell checker.) It's a big change but some parts could be adopted and applied in small chunks as you see fit. It contains all the current functionality although you might not recognize it at first because I've changed some of the command names and concepts. For example, 'Syntax Format' replaces 'User Defined Languages' and 'Languages'. I've mostly brough similar things together but in a few cases, Run and Macros, I've split the functionality up.
There's a few areas where I don't know as much as I should. I've taken a punt with these. They are 'Run' which I've changed 'Commands' and ...
At the last minute I realised I've mis-used the ellipses mark (..) on menus. I decided to get this out rather than delay publication any longer. I'll add proper cascading menu marks, tick-marks for alternatives, and ticks for 'On' status if there are requests for a further iteration of this proposal.
I've also put myself in the firing line of plugin developers for daring to suggest uniform naming conventions in the Plugin menu, although this need not affect their program names.
Alright, Fire away!
Overview of proposed changes to NP++ menus: http://notepad-plus.wiki.sourceforge.net/space/image/64x64/gw_proposed_nppp_menu_structure_overview_1.00.gif
Elaboration of cascading menus, part 1: http://notepad-plus.wiki.sourceforge.net/space/showimage/gw_proposed_nppp_menu_structure_sub-menus_1_1.00.gif
Elaboration of cascading menus, part 2: http://notepad-plus.wiki.sourceforge.net/space/showimage/gw_proposed_nppp_menu_structure_sub-menus_2_1.00.gif
--Gr3gw
> (a) reducing the number of menus (and therefore choice when looking for something)
IMO, all the sub menu are needed.
> (b) reducing the number of items on menus particularly Edit,
> the longest (and therefore assisting those using lower
> resolution screens and reducing choice when looking for something)
(Almost) All the Notepad++ features are listed in the menu to help users to learn them. So it's important to not remove commands from the menu.
> (c) clustering similar functions (so there are fewer places to look for something)
That's the solution to make menu shorter and cleaner.
In the next release, the sub-menu Edit/View and Languages are improved - these 3 menu will be cleaner and shorter. User can access to every single menu command even under a 640x480 display.
Don
Here's the coreect URL for the 'Overview of proposed changes to NP++ menus':
http://notepad-plus.wiki.sourceforge.net/space/showimage/gw_proposed_nppp_menu_structure_overview_1.00.gif
--Gr3gw
at least, tabs menus as in the following image
http://upload.wikimedia.org/wikipedia/en/archive/e/e1/20090310044825%21Homesite-2.5.gif
I'm just not sure how much development it takes to get those menus working. Your picture looks like the way HTML-Kit displays items.
In a nutshell, this may work right on Win 2K/XP/Vista, but if N++ is supposed to run under Win9x/ME then it may not be a good idea.
CChris
Sorry, Greg, but I'd be mostly with Don about your proposal.
The only point where I might agree with removing some stuff regards the Format menu. To me, it seems that the current encoding format is something that doesn't change often, so its functionality could be moved to a new tab of the Preferences dialog.
Adding to the c) item:
Some TextFX submenus are quite lengthy, so I'd appreciate seeing them shortened using inner submenus. Convert and Viz are obvious candidates, and Edit might benefit as well.
Another option would be for long menus to split into mandatory and nonmandatiry items. Mandatory items would be displayed regardless. Non mandatory items would be displayed according to individual yes/no specific UI settings, configurable on the fly from Preferences, and all on by default. That way, users can clean menus the way they like better, and new users wouln't miss a single command. Of course it would be tedious to implement...
CChris