Isn't the select project list a good example of a drop down that can be replaced by an ajax autocomplete textfield ? -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com
Adrian Rossouw wrote:
Isn't the select project list a good example of a drop down that can be replaced by an ajax autocomplete textfield ?
I think Ber had made a patch for it. The problem is that for users who don't know the possible project names, it is not really an improvement. Also, firefox for example already seeks for the correct module base on the chars I type. Cheers, Gerhard
-- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com
Adrian Rossouw wrote:
Isn't the select project list a good example of a drop down that can be replaced by an ajax autocomplete textfield ?
Sorry, but -1. It's a good idea in theory, but fails in any of the following scenarios: 1. People new to Drupal who don't know what that box is for and don't know the specific names of projects will be totally confused on what to do with it. 2. When you forget the exact name of a project, you have to either a) futz around trying different letters, or b) keep a copy of http://drupal.org/project/Modules/cvs open 3. The above still won't help with projects like "Drupal.org maintenance" and "Documentation" so there will be projects that are totally missed by people who don't already know their exact name. As Gerhard mentioned, Firefox (and Opera too) has the behaviour where when you highlight the drop-down and press "dr" you're jumped down directly to the "Drupal" project. I just checked and it looks like IE doesn't have this (so I can see why that would get *really* annoying if that's what you're using). But imo it's not worth killing the usability of the project selection mechanism for the little browser that can't. ;P -Angie
After categorizing modules put a dropdown for each hierarchy level, and do a top-down filtering. Just a thought.
Related to enhancements to the project module - I think it would be nice if there was a field where you could enter the url to the nid of an original issue when you are marking a duplicate issue in the project module as 'duplicate' and then the original issue link is themed onto the issue report node. The ajax selector that Ber created in the clipper.module for finding a node by title (and then add a filter on there so only project node titles show up and also the option to write in the nid instead of title) could help this work. thoughts? Adrian Rossouw wrote:
Isn't the select project list a good example of a drop down that can be replaced by an ajax autocomplete textfield ?
On Friday 17 March 2006 17:55, Ian Ward wrote:
Related to enhancements to the project module - I think it would be nice if there was a field where you could enter the url to the nid of an original issue when you are marking a duplicate issue in the project module as 'duplicate' and then the original issue link is themed onto the issue report node.
This is a nice idea - issues marked dupes can be easily lost when one isn't looking hard enough... ;) I posted a feature here [1] which is along similar lines. Sometimes a new issue (appearing in the tracker, at the top of recent lists, feeds etc) will be marked as a duplicate of a long-standing, old issue sitting near the bottom of the queue. The new one is 'lost' in issue lists, and the old one isn't easily found/linked to. The idea in [1] was to somehow 'bump' the old issue with an automated message: This issue has been reported in duplicate issue [.../node/n] or something. This would probably need an additional dupe URL/nid field as Ian describes. paul [1] http://drupal.org/node/44162 -- paul byrne ------------------------------------- e-mail: paul@leafish.co.uk web: http://paul.leafish.co.uk http://www.leafish.co.uk -------------------------------------
participants (6)
-
Adrian Rossouw -
Angie Byron -
Gerhard Killesreiter -
Ian Ward -
Michelangelo Partipilo -
Paul Byrne