Re: Number of clicks with new Admin menu
<[email protected]> Thu, 16 Oct 2003 07:44:41 -0700
| Newsgroups | gmane.comp.php.drupal.user |
|---|---|
| Message-ID | <8C5620B2AC9DE91-840-37DD@APP4> |
Jonathan, I prefer the re-organized top-level nodes as well. But this re-organization required re-drawing my mental map to understand how all of the sub-nodes have been re-organized into these parents. I think the idea of allowing people to customize their menu structure is novel, but wonder how many users need this kind of functionality. An overview of functions might help fit many scenarios with fewest clicks. What happens with a narrower organization is that a lot more exploration and learning is required to find your way to the functions buried deep within the tree. This is ok and is perhaps favorable to some. What works in the narrow versus broad debate comes down to preference. So with that in mind, I think an overview works to supplement the drill-down menu. Visually, it is possible to chunk those admin functions so that they can be viewed in a non-noisy way. WHile this may not be the best example, a related view of taxonomies on my blog using taxonomy_html helps to get an overview of topics without requiring a user to drill down through top-nodes. http://urlgreyhot.com/drupal/taxonomy_html -Michael -----Original Message----- From: Jonathan Chaffer <[email protected]> Personally I prefer the narrow menu and in fact wish it were even more streamlined. But that's my personal preference. There are really two issues here: 1) We need an intuitive and clean menu layout. This is obviously a tricky task and has and will inspire many debates. 2) We need a way for people to fairly easily customize the menu structure if what we decide on doesn't suit them. I don't necessarily think that we have to make this an option in the admin pages (it might complicate support if we can't direct people to a link in a particular location), but people comfortable with modifying source shouldn't encounter too many roadblocks in moving things around. Currently this is difficult because of reliance on arg() calls; modules are built around pages having particular URI's. I'm working on patches to remove this reliance in 4.4. Then it will be as easy as going to the module's _links hook and changing the paths in one place, and everything should work. -- Jonathan Chaffer Applications Developer, structure:interactive (616) 364-7423 http://www.structureinteractive.com/ -- [ Drupal user list | http://list.drupal.org/ ] [ http://lists.drupal.org/options/drupal-user/jibbajabba-lists7543%40mailblocks.com ] -- [ Drupal user list | http://list.drupal.org/ ] [ http://lists.drupal.org/options/drupal-user/gcpdu-drupal-user%40gmane.org ]