Closed (won't fix)
Project:
Bot
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 Jun 2008 at 19:32 UTC
Updated:
26 Jun 2008 at 00:57 UTC
Use tabs instead of normal menu items. This makes things look a bit nicer and seems to make the Bot administration look more Drupal-friendly.
Screenshot: http://drupal.org/files/bot_tabs.png
| Comment | File | Size | Author |
|---|---|---|---|
| bot_tabs.patch | 6.19 KB | robloach | |
| bot_tabs.png | 167.03 KB | robloach |
Comments
Comment #1
robloachSorry... Screenshot: http://drupal.org/files/issues/bot_tabs.png
Comment #2
morbus iffThe problem with this is that tabs are generally a set number - you know all the tabs that will ever exist, and you don't expect them to change location. I don't know of any Drupal core instance (save for the user/* page) that has an always growing set of tabs. And, on a good day, the bot could have dozens of modules created for it. Dozens of tabs would badly wrap, and make any single tab be harder to find.
Comment #3
morbus iffI won't argue that it doesn't looks nicer - but I argue that it's not as scalable/usable going forward.
Comment #4
robloachOne example of a menu tabs page that has an ever growing amount of tabs is admin/build/themes/settings. If you enable 10 themes to your system, there are 11 tabs. The tabs were just an idea, not a requirement. We'll see how it goes, I guess :-) .
Comment #5
morbus iffAnother good one. It's a UI technique that just doesn't scale, in my opinion. Whereas I personally find it odd to have 11 themes installed, I don't find it outside the realm of reason to have 11 bot modules installed. Could you imagine if every single node.module used tabs on, say, admin/content/node-settings? That's the corollary you're making - if all bot related modules should be grouped as tabs, than so should all node related modules. I'm pretty sure that rationale isn't going to make it into core.
Comment #6
morbus iff