This is the same as core issue #1296876: Make dependency list hidden on modules page until requested. After the turn the discussion took at #538904: D8UX: Redesign Modules Page, I don't know if #430180: Move module_filter (or its functionality) in core for D8 will be ever accepted, so we better implement this here if we want to have it:

...as opposed to the current mess:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

klonos’s picture

...uploading mockups from skitch.com locally so they don't get lost.

petsagouris’s picture

I consider this as a really good thing to do with this module. It will elevate the usefulness.

greenSkin’s picture

I like it but would want to see the ability to present the user with all the information upon request. Perhaps a link along with the Permissions/Configure links - use just an image rather than include the text "Dependencies" (if the image could justly signify what it's for). Maybe use a contextual link - like that used for blocks when moused over - that could enable/disable showing all dependencies. Or we just though it on the settings page. I'd rather have it at easier access than on the settings page but I'm willing to concede there if it otherwise means not showing all dependencies.

klonos’s picture

The dependencies could be hidden in a collapsible fieldset or something like that. We can have the ones that all dependencies are met be collapsed by default and their fieldset label be "All dependencies are met" in green. Users can show the list on demand by clicking the text. The ones with unmet dependencies could have a red "Missing dependencies" text and be collapsible (but open by default).

petsagouris’s picture

I came across the Clean Module List that is supposedly doing this.

klonos’s picture

Thanx for the link to this project "patrida"! Does it play nice with Module filter?

Edit: it only offers the option to either hide or show *all* the dependencies. There's no option to only hide dependencies that are met, so I still lay my hopes here ;)

petsagouris’s picture

hehe, well from your testing it appears that it does provide for a base to kick things off. If I get round to it I may see what I can do to provide my interpretation of the issue as a patch in a couple of days.

I am guessing that it would be wise to actually go ahead and implement a "Settings" local task tab for the module page so that defaults can be set. Inside that apart from the defaults for the "Enabled", "Disabled", etc options for the search filter, we could provide an option for the display mode separately for the "Required by" and "Requires" lists of modules.

klonos’s picture

I am guessing that it would be wise to actually go ahead and implement a "Settings" local task tab for the module page...

That would indeed be very nice UX-wise (but I believe that this idea deserves its own issue). The Update status advanced settings module does a similar thing for its settings, but in its case it uses the already existing "Settings" tab in the "Available reports" page (../admin/reports/updates/settings). I guess we should keep the same pattern in order to be in tandem with what users are used to in the UI ;)

klonos’s picture

...actually I think that it was mentioned before (I believe here: #538904: D8UX: Redesign Modules Page - don't remember - that's a very long issue) that there is consideration to merge the "Available updates" page with the modules page. So, I guess that the updates settings tab will be moved as a tab of the modules page in D8 anyways.

klonos’s picture

klonos’s picture

...and here's the mockup that introduces a "Settings" tab in the modules page (you can also see the available updates suggestion in practice):

... I'd like to call your attention to the "Settings" tab (1) at the top of the page. Let's assume, for the sake of argument, that within that tab users will be given the option to set defaults for all form fields on this page, as well as enable/disable specific features. ...

klonos’s picture

Can we have a word from the maintainers on this one please? Do you find it useful? Do you plan to implement it when time permits?

klonos’s picture

Issue summary: View changes

...using locally uploaded mockups instead of the ones @ skitch.com

klonos’s picture

Issue summary: View changes

...mistyped tag

Leeteq’s picture

Issue summary: View changes

The current last version does hide the dependency information now, but I think it should also contain a per-category checkbox to "show all/hide all" so that all modules in the given category expand/collapse conveniently from just one click in the category header.

smustgrave’s picture

Status: Active » Closed (outdated)

With D10 now out going to putting all the focus on the 4.x version of this
module supporting D9 + D10.

Will keep an on the 7.x-2.x branch for reviews but no active work will
probably happen