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

CommentFileSizeAuthor
bot_tabs.patch6.19 KBrobloach
bot_tabs.png167.03 KBrobloach

Comments

robloach’s picture

Priority: Normal » Minor
Status: Active » Needs review
morbus iff’s picture

The 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.

morbus iff’s picture

I won't argue that it doesn't looks nicer - but I argue that it's not as scalable/usable going forward.

robloach’s picture

One 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 :-) .

morbus iff’s picture

Another 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.

morbus iff’s picture

Status: Needs review » Closed (won't fix)