1st) The selection of tools available in the 'Tools' menu should depend on the document class of the currently selected file in the editor. This would save entries in the 'tools' menu and shortcut keys. When I write <html> code, I don't need the C++ compiler to be available as a tool in the menu. When I write C++ code, I don't need HTML Tidy to be available as a tool in the menu.
I would prefer to use the same shortcut key to launch either the compiler or Tidy, depending on what I'm working on.
2nd) It should generally be easier to create document classes, tool entries and shortcuts in one dialog, and to save those settings in text files.
I've been using TextPad for... let's see... about 10 years now almost (is that possible?) and the enhancement you're suggesting is something I requested of Helios sometime around 2000 or 2001. I was almost shocked to see a new version on the website this morning after so many years of tranquility, and naturally looked straight away to see whether the Tools options had been placed into the Document Class options structure.
...Alas!!
Because after all what you are saying is exactly right: When a developer needs to use different tools for different document classes then it's most convenient to not have the toolbar cluttered with all sorts of irrelevant tools associated with irrelevant document classes. So �'d like to support your request by placing my vote beside yours:
- The option to associate tools with one, seeveral, or all document classes
Funny to find this thread, I was about to suggest the same thing.
I agree wholeheartedly with the original suggestion, esp. that the same shortcut keystrokes would call a different tool, depending on the document class of the currently edited document.
