I thought I'd post one of my palettes, so we could discuss how we organize our palettes. I believe this topic has been covered before, but what's a forum without repeated topics?
Here's a palette I use while in the KM Editor. I have it on a second monitor:
I make heavy use of icons, and group things using separators. Here's what the macros look like in the editor:
Thanks, @DanThomas, for posting.
I’m always interested in learning and discussing palette ideas.
In the sample above:
1. Too many repeating icons.
Use icon just for first macro of each type.
Those of similar type below icon are blank.
Your eye will focus more easily.
2. Use solid underscore in place of dashed lines.
Again, easier on the eyes.
3. Condense macro titles.
Faster recognition.
Smaller pallet size.
Instead of “Find Macros that use Selected Sub-Macro”, use “Find Subs”
4. In macro titles, reverse order of verbs and nouns so noun comes first.
Noun is almost always the most significant word.
Replace “Copy as Execute Macro” with “Execute a copy”
5. Instead of “(option+M)” use actual key cap symbol: ⌥ M
6. Change palette colors to black or dark letters on light background.
Always easier to read than “reverse” white letters on a dark background.
(Majority of palette designs in KM are “reverse” – trendy, yes, but poor human interface design.)
All of your suggestions are reasonable, and I disagree with all of them. I'm sure they work for you, as I am equally sure what I've chosen works for me.
Funny how two people can come to opposite conclusions, isn't it? That's why customization is great!
But just for fun, I'll address each of your comments:
Too many repeating icons.
Use icon just for first macro of each type.
Those of similar type below icon are blank.
Your eye will focus more easily.
I have severe ADD, and picking out things is a strange and incomprehensible set of internal rules for which I have no explanation. These icons work for me, along with the grouping and order, and of course macro names. As I said, I can't really explain it.
Use solid underscore in place of dashed lines.
Again, easier on the eyes.
I tried that, and I actually like the dashes better. Again, no idea why.
Condense macro titles.
Faster recognition.
Smaller pallet size.
Instead of "Find Macros that use Selected Sub-Macro", use "Find Subs"
This goes to my programming style. I almost always name functions, subroutines, whatever, with full names. My brain would read "Find Subs" and go "Huh?" So I'm used to reading long names.
In macro titles, reverse order of verbs and nouns so noun comes first.
Noun is almost always the most significant word.
Replace "Copy as Execute Macro" with "Execute a copy"
I actually totally disagree with this. I ask myself what I want to do. The answer always comes back in verb-noun format. I want to "go to a macro". I want to "make macro alias". etc. It's also the programming standard I use for most of my functions. Verb-noun.
Instead of "(option+M)" use actual key cap symbol: ⌥ M
I always have trouble remembering that ⌥ means "option". Don't know why - perhaps my PC upbringing.
Change palette colors to black or dark letters on light background.
Always easier to read than "reverse" white letters on a dark background.
(Majority of palette designs in KM are "reverse" -- trendy, yes, but poor human interface design.)
I went through all the color schemes, and I like this one best. It just works for me.
As I said, all personal preferences. Love the fact that there's so many options!
I emphatically support the verb-noun construct like you, @DanThomas. In a former life, I wrote a lot of instructional materials and also performed a great deal of UI usability testing (think: menu choices). In both cases, verb+noun always won.
I'm sure they work for you, as I am equally sure what I've chosen works for me.
Emoji actually makes a pretty cool divider.