Package/group "API" for module administration
Hi all, As there are many API modules around (the ones just to be enabled when other module requires it) and also there are tons of different modules and packages I'd like to propose creating an "API" package to be shared by all these modules. This way all these modules would be hidden somewhere in the module list not creating extra groups that are really not needed. All we need to do is to add package = API in our module's info files. If this sounds good for a few module maintainers we can just do it. Cheers, Jose
I would suggest contacting each of the maintainers and ask if they are on board. The use of "package" is out of control anyway. Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
________________________________ From: Jose A. Reyero
As there are many API modules around (the ones just to be enabled when other module requires it) and also there are tons of different modules and packages I'd like to propose creating an "API" package to be shared by all these modules.
This way all these modules would be hidden somewhere in the module list not creating extra groups that are really not needed. All we need to do is to add package = API in our module's info files.
If this sounds good for a few module maintainers we can just do it.
Already suggested that ~4 years ago. Feel free to re-open http://drupal.org/node/113412 Thanks, sun Am 09.10.2011 11:31, schrieb Jose A. Reyero:
Hi all,
As there are many API modules around (the ones just to be enabled when other module requires it) and also there are tons of different modules and packages I'd like to propose creating an "API" package to be shared by all these modules.
This way all these modules would be hidden somewhere in the module list not creating extra groups that are really not needed. All we need to do is to add package = API in our module's info files.
If this sounds good for a few module maintainers we can just do it.
Cheers,
Jose
On 09/10/11 17:26, Daniel F. Kudwien wrote:
Already suggested that ~4 years ago.
Feel free to re-open http://drupal.org/node/113412 Yes, but that is a category for module listing on drupal.org, isn't it?
I'm suggesting just a module package so they should up under that package on your site's module listing page. Anyway I think I'm going to start using it, and see if other maintainers would like to join.
Thanks, sun
Am 09.10.2011 11:31, schrieb Jose A. Reyero:
Hi all,
As there are many API modules around (the ones just to be enabled when other module requires it) and also there are tons of different modules and packages I'd like to propose creating an "API" package to be shared by all these modules.
This way all these modules would be hidden somewhere in the module list not creating extra groups that are really not needed. All we need to do is to add package = API in our module's info files.
If this sounds good for a few module maintainers we can just do it.
Cheers,
Jose
Am 12.10.2011 11:18, schrieb Jose A. Reyero:
I'm suggesting just a module package so they should up under that package on your site's module listing page.
A d.o category/tag would make sense to me, but a package/category on the Modules page would not. Over the years, module packages have been (ab)used to group modules by "type of functionality". "API" does not describe a certain functionality. While your idea makes some sense for the case of installing/enabling modules, it's going to be highly confusing for users that want to *disable* functionality. E.g., enable a "Foo UI" module in the "Bar" package/group, and Drupal tells you that "Foo API" module also needs to be enabled. Fine. Test-drive, dislike, go back, and disable "Foo UI" module, and... an epic journey to find "Foo API" module begins. Related issues: - Smarter UI/API separation for modules: http://drupal.org/node/937814 - Searchable modules page: http://drupal.org/node/396478 sun
On 10/12/2011 03:52 PM, Daniel F. Kudwien wrote:
E.g., enable a "Foo UI" module in the "Bar" package/group, and Drupal tells you that "Foo API" module also needs to be enabled. Fine. Test-drive, dislike, go back, and disable "Foo UI" module, and... an epic journey to find "Foo API" module begins.
Another related issue: disable any module you want without caring about dependencies: http://drupal.org/node/468208 -- Klaus Purer This E-Mail contains a digital signature and can be verified with this PGP|GPG Public Key: http://web.student.tuwien.ac.at/~e0426223/key/kp.asc
participants (4)
-
Daniel F. Kudwien -
Jose A. Reyero -
Klaus Purer -
Ms. Nancy Wichmann