Better token lists

Crossposted to usability gruop.

The three modes that I've seen people use are:

1. The one in sirkitree's screenshot in the original post.
2. Pathauto style: does it's own processing to get a list of tokens that will work for the current scope (e.g. nodes). Reduces the number of tokens somewhat, but not a ton.
3. Don't include this advice under the field, instead say "You can use tokens here like [foo], [bar], and [baz] or see the detailed help page for more details." Then put the full list in the help page. Ubercart does this in several places.

I've thought some nice additional styles though never implemented them (nor seen them implemented).

1. A jquery based filter mechanism at the top of that big list.
2. An autocomplete style mechanism that would be most useful for single line textboxes.

Anything else?

--
_{Growing Venture Solutions | Drupal Dashboard | Learn more about Drupal - buy a Drupal Book}

Here's what I've decided upon.

First limit the scope. This cuts down on the amount of tokens as Greg suggests in #2 with the Pathauto style.
Then make each type a collapsible fieldset, resulting in the following:

Good to report back on what you actually chose to do. Thanks. Seems like a fair solution. Presenting long long, very long lists of stuff is a recurring UI problem and I think you picked the right option for this case.

Only issue with this is that the fieldset titles become very important because that is the only thing you get to base your initial choice on. You might consider dropping the repetitive 'tokens' from all nested fieldset titles, it's pretty clear we're administring tokens already, no need to keep saying it. Omit needless words.

My ultimate goal is to customize Mail Templates that are used when Drupal 5 sends out subscription notices--using tokens to effectively pick and choose which parts of the full node that get sent out to the subscribers.

The standard page for editing a mail template shows a list of tokens (!title, !body, !full_node . . .), but I'm thinking there has to be more than that. The problem is that I don't know how to find or produce a "dictionary" of available tokens.

I've installed the Token module, btw. Apart from a somewhat obscure appearance on the admin/build/modules page, I can see no sign that the module is doing anything.

Is there a script I could just paste (I'm no PHP wizard) into the body of a page that would reveal a dictionary of tokens? I'm especially interested in finding a token for attached files.

Wow, that's cool - especially the one-click & scroll-back-into-view feature ;-)