Improvement requests :
K-Meleon Web Browser Forum
Splitting up the old macros.cfg file into a folder with individual macro files was a very good idea. Why not do the same for menus? It's probably brought up before, but if not, here's my 2 cents:
We start with some folders called menus: an "all-user" version in the main program folder, customised copies in the individual user profile folders.
Each menu will be a subfolder of menus, so we'll get subfolders called file, edit, tools, context menu, etc.
Submenus within a menu will be a subfolder of the corresponding menu folder, so we'll get folders called toolbars and zoom within the view folder, folders called privacy and proxy within the tools folder, etc.
Just like we have .kmm files for macros, we'll make .men files for menu entries. These files are simply snippets of the current menus.cfg files, just like .kmm files are snippets of the old macros.cfg file.
We need two more things: a way to tell the browser how to display the menu entries within a menu, and a way to add separators between (groups of) menu entries.
Separators can be added by creating empty files called x separator.men in the appropriate folder, and the order in which menu entries, submenus, and separators appear can be specified by starting their file and folder names with a number.
For example, a menu that looks like:
can be built from the following files and folders within a folder called page context menu:
When the entire menu structure matches a hierarchical file-and-folder structure, moving or duplicating menu entries from one menu to another will be as simple as dragging and dropping (or copy/pasting) files and folders, which is way easier than the current clumsy navigation through a crowded menu.cfg file. Few people manage to edit menus.cfg without getting lost, but everyone knows how to drag and drop files from one folder to another and how to change a filename: Windows itself will act as a graphical interface to customise K-Meleons menu layout.
Use this forum to talk about a feature you're missing.
Modular menus (just like modular macros) ?
Posted by:
666
Date: August 17, 2007 03:27AM
Splitting up the old macros.cfg file into a folder with individual macro files was a very good idea. Why not do the same for menus? It's probably brought up before, but if not, here's my 2 cents:
We start with some folders called menus: an "all-user" version in the main program folder, customised copies in the individual user profile folders.
Each menu will be a subfolder of menus, so we'll get subfolders called file, edit, tools, context menu, etc.
Submenus within a menu will be a subfolder of the corresponding menu folder, so we'll get folders called toolbars and zoom within the view folder, folders called privacy and proxy within the tools folder, etc.
Just like we have .kmm files for macros, we'll make .men files for menu entries. These files are simply snippets of the current menus.cfg files, just like .kmm files are snippets of the old macros.cfg file.
We need two more things: a way to tell the browser how to display the menu entries within a menu, and a way to add separators between (groups of) menu entries.
Separators can be added by creating empty files called x separator.men in the appropriate folder, and the order in which menu entries, submenus, and separators appear can be specified by starting their file and folder names with a number.
For example, a menu that looks like:
Open page in IE Create shortcut on desktop Save page as ------------------ Copy Text Select All Selected Text > [submenu] ------------------ Page Properties > [submenu]
can be built from the following files and folders within a folder called page context menu:
010 Open page in IE.men 020 Create shortcut on desktop.men 030 Save page as.men 100 separator.men [an empty file] 201 Copy Text.men 202 Select All.men 220 Selected Text [a folder] 400 separator.men [an empty file] 501 Page Properties [a folder]
When the entire menu structure matches a hierarchical file-and-folder structure, moving or duplicating menu entries from one menu to another will be as simple as dragging and dropping (or copy/pasting) files and folders, which is way easier than the current clumsy navigation through a crowded menu.cfg file. Few people manage to edit menus.cfg without getting lost, but everyone knows how to drag and drop files from one folder to another and how to change a filename: Windows itself will act as a graphical interface to customise K-Meleons menu layout.
English