It is a useful module when site developers wants to fall back to the core modules in a one go.
while i was testing it i thought a different and enhanced approach would be possible;

currently it is essentially functions as a 'filter' to all modules for one category the 'required core' modules

instead what if it features a full filter of the modules based on module categories that on modules page 'toggle able'

a module filter that a-la the content filter of nodes on;
admin/content/node

basically contrib_toggle enhances the core admin/modules section with a module filter and a 'check all' option button

for example
-------------------------------
filter drop down select by
- [module status] (active, passive)
- [category] (CORE - OPTIONAL, CORE - REQUIRED, CCK, ADMINISTRATION, DATE/TIME, OTHER, VIEWS etc.)
-------------------------------

would be a further improvement/enhancement to this module and to Drupal core.

Comments

ica’s picture

ica commented

here a simpler jq selector example of a check all/ check/off options rather than a full drop-down filtering
http://jqueryui.com/download (the red indication)

  • (default) Deselect/Select all components (modules)
  • Select/Deselect all individual components (modules) group/category of modules
    • babbage’s picture

    babbage commented

    That's an interesting idea. The main barrier could be that the categorisation of modules within Drupal isn't nearly as clear as in that jQuery UI example, which would mean that sometimes the set that would be activated or deactivated by such a link would be either too narrow or too inclusive. That said, Contrib Toggle already handles dependency management no matter how the modules are categorised, so it would only be a question of how optimal the functional outcome was, not whether it worked or not.

    I'll consider it in future UI changes to the module that are already planned...

    ica’s picture

    ica commented

    definitely! Drupal module categorization needs some thinking love and finesse as their numbers hit 1500+ and growing per day (important slice of them have overlapping or slight diffrences and some of them complimentary that would be better combined)

    Setting a finer categorization rules would also help other modules such as plugin_manager.module, admin.module and imho if it can be cracked and proven to work with conrib module an it may -and should go to the core on D7 or D8 for a even more smarter Drupal.

    Contrib Toggle's existing dependency handling management for the core modules is nice one

    -for instance there is another module quick-admin-modules.module does exactly this for slight different purpose but overlaps when you think about doing things differently and combining efforts if possible to into one modules selector with dependency+categories? just made me to think

    http://drupalmodules.com/module/quick-admin-modules

    mind the example on http://jqueryui.com/download jq selectors does multi selection inplace/in one click on example

  • Select all components
    Components (25 of 25 selected)
    Deselect all component + Theme block on the right selectors.

    ~It's easier to point out surely harder to do it as usual. I am no js or PHP coder to make a real contribution on that front though...

    • babbage’s picture

    babbage commented

    In fact, some of the code in Quick Admin modules was used in the development of Contrib Toggle. The fundamental difference between the two is that Contrib Toggle works, whereas Quick Admin modules appears to work but in fact does not disable the modules you have marked for being disabled.

    As for categorisation, the current system lets a module developer create whatever kind of categories they like for where their modules appear, but also allows any other developer to also put their modules into those categories. Thus, it is a fairly chaotic process and it would be hard to predict what any one client site would look like given the virtually infinite number of combinations of module selections there would be...