Groups.drupal.org is a part of the drupal.org group of sites. Logging in on this site requires an account on the main drupal.org site. If you do not have an account on drupal.org, you will need to create one, log in over there, and then come back here where you should automaticall
Thanks!
Group categories
UX topics
- contrib-ui (12)
- core-ui (31)
- Help system (2)
- nodeform (7)
- Process (6)
- Resources (6)
- taxonomy (1)
New groups
Group notification s
Group events
-
2009-12-01 12:30 - 13:15
Ical feed for upcoming events in this group. 


three modes I've seen
Crossposted to usability gruop.
The three modes that I've seen people use are:
I've thought some nice additional styles though never implemented them (nor seen them implemented).
Anything else?
--
Growing Venture Solutions | Drupal Dashboard | Learn more about Drupal - buy a Drupal Book
I think a jQuery text filter
I think a jQuery text filter textarea at the top of the list of tokens would be ideal. Just type in 'menu' and the list is immediately pared down to the ones that contain the text 'menu,' and there's still room for the descriptions below each token. There are jQuery plugins that make this really easy, though I've mostly seen them used on table rows.
Popunder? I'm not sure what
Popunder?
I'm not sure what does it call. But the same as Greybox image module. Help dialog popup within the admin page.
Popups
Yes popups would be good for this. Especially combined with the external help page link as greggles mentioned. I think I'll go that route, but I REALLY like the jQuery filter idea too... hrm...
Something like the jQuery
Something like the jQuery Tag Suggestion plugin (http://remysharp.com/2007/12/28/jquery-tag-suggestion/) perhaps?
As for the long list of tokens, maybe we can follow the how Views allows you to Fields filter by categories.
Here's what I've decided
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 job!
I noticed this is what you implemented with activity-2.x, keep up the good work. This method improves productivity by 1000%.
Good to report back on what
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.