As of the latest dev (February 1, 2012) I've removed the tweaks to the "Save configuration" button. No longer does it fall just below the tabs, nor will it always reside on screen. I've done this in favor of a more generic solution that can be used on more than just the modules page. Please take a look at and evaluate my proposed solution: Page actions.

The following is a screenshot of how it looks by default. Themes should be easily able to alter how it looks.
Screenshot

The module is obviously in very early stages, but I want to get everyones feedback on whether this is a good thing or not.

Comments

petsagouris’s picture

StatusFileSize
new235.61 KB

I'd rather have that on the top right.
This is the button that will be pressed 80% of the times you are visiting this page.

The whole "save button, module filter area, table headers" area should be actually made sticky.

Please take a look at the mockup:

proposal02.png

Suggestions that are not in the mockup:

  • Further work on this will deal with the "extra high" appearance of that area, which actually involves putting the checkboxes on the right of the filter input and thus giving the ability to condense the area vertically.
  • The vertical tabs for the packages can easily be replaced with a drop down since having to scroll in order to see all the items, actually cancels the usability that they vertical tabs provide. It would make sense if we could see more than one package at a time but this is not the case.
rogical’s picture

StatusFileSize
new131.33 KB

I have the same issue while I enable a field module, the list is too long, I have to find the 'Save xx' in button, that's not good.

Some users may not want to use another module, so is it possible just make a patch to module filter to set the place of action?

thanks,

dd

klonos’s picture

I was thinking that perhaps the old chunk of code should stay in place and get wrapped around an if statement to check for existence of the page_actions module. If found use that, else use the old code. This would help provide an out-of-the-box experience for users (IOW without "forcing" them to add and enable yet another module). At the same time this method would allow for people that find the page_actions useful and use it in their sites anyways to use that instead ;)

greenskin’s picture

Status: Needs review » Fixed

The module will now utilize page_actions if it exists, otherwise the previous functionality to page_actions is available (namely the dynamic positioning of the save button).
http://drupalcode.org/project/module_filter.git/commit/f0d8192509adacff1...

klonos’s picture

Perfect! ;)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

Issue summary: View changes

Fixed incorrect dev date.