Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modules page cleanup #300

Closed
jenlampton opened this issue Aug 15, 2014 · 7 comments
Closed

Modules page cleanup #300

jenlampton opened this issue Aug 15, 2014 · 7 comments

Comments

@jenlampton
Copy link
Member

  1. Add a search box at the top like Drupal 8 has done
  2. Hide the requires / required by information
  3. Add a drop-button in the operations column (default: configure)
@quicksketch
Copy link
Member

Merged in backdrop/backdrop#424. This looks amazing! Thanks!

@klonos
Copy link
Member

klonos commented Aug 23, 2014

I'm an old-timer. I like to see dependencies. So, how does this work now? Do dependencies only appear when not met?

@quicksketch
Copy link
Member

@klonos there's a "more" link after the description that you click to show all dependencies, they're just hidden until you click on it.

@klonos
Copy link
Member

klonos commented Aug 23, 2014

Ahh! Thanx.

I thought that the 'more' link was to take you to a backdrop/drupal website page with more info about the module. Now I got it.

@docwilmot
Copy link
Contributor

I suggest the search box also find dependencies. That way when you just installed a new module and search for it, you don't have to hunt down the dependencies separately. And optionally display the contents of the "more" link so its obvious.
I know bd will ask if you want to enable dependencies if you dont enable them first, but sometimes I prefer to enable things one by one, in case hell breaks loose.

@docwilmot
Copy link
Contributor

Optionally, newly installed modules could be displayed in a separate container at the top of the modules page, with their dependencies, to make them easier to find.

@klonos
Copy link
Member

klonos commented Apr 30, 2018

...for historic reasons, @docwilmot's suggestion was captured in #532

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants