I was thinking of a real simple interface change just to group things together. With the increased usage of the _info hook the install api and dependency checking will likely bring, adding 1 field to it (ie: function module_info($key ='name') { $info['bundle'] = t('E-Commerce'); return $info[$key]; } ) will allow us to visibly group the modules together. Inter-module dependencies are part of this ticket (http://drupal.org/node/18447), and it should probably go into core first. On 27 Mar 2005, at 1:33 AM, Chris Messina wrote:
I think that "module bundles" that somehow express dependency is a great idea. This will be necessary for a number of CivicSpace modules, so if we could work on this sooner than later, I think the benefit would be apparent. eCommerce would obviously be one of the first beneficiaries.
This same grouping technique could be applied to input filters and -- gasp -- might even benefit from the "show/hide" functionality slowing making its way into Drupal now.
+1 from me!
Chris
On Sat, 26 Mar 2005 21:22:27 +0100, adrian <drupal-devel@drupal.org> wrote:
Issue status update for http://drupal.org/node/19477
Project: Drupal Version: cvs Component: module system Category: feature requests Priority: minor Assigned to: Anonymous Reported by: jjeff Updated by: adrian Status: active
Once this is in core, we could use the hook_info function to provide a 'bundle' field, and then modify the module list to group modules by bundle. (perhaps even on a separate tab? who knows). http://drupal.org/node/18447
adrian
Previous comments: ---------------------------------------------------------------------- --
March 26, 2005 - 03:53 : jjeff
It would be nice if the admin/modules listing grouped multiple modules that resided in subfolders of the main modules directory. This way module collectives (like ecommerce or massmailer) would all show up in the same area of the module listing. It would make enabling/disabling these modules a lot more intuitive and also make it clear which modules were part of a group. Single modules in a subfolder would not exhibit this behavior. Just a thought. -Jeff
---------------------------------------------------------------------- --
March 26, 2005 - 05:44 : mathias
Being the author of the ecommerce package, I have to give a big '+ 1' to this as well. Why was this behavior removed? I could see a re-implementation similar to our access control GUI where the first level of folders are displayed with the modules underneath, providing more context for the users.
-- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com