Split up module into component parts
| Project: | Tweakbox : drupal tweaking modules |
| Version: | HEAD |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
This module should really be split up into its separate components, and each given an appropriate name.
- tweakbox doesn't mean anything. it's hard to find it if you're looking for teaser control
- it's hard to figure out what it does from the name. 'tweaking' covers everything under the sun.
- it's an arbitrary grouping of functions. It's what the creator of this module felt was useful for their site, which is great -- but other people have completely different sites, and completely different needs. Modules or packages of modules should have clear, distinct uses, not be a bundling of stuff.
I'm attaching a standalone teaser control module I've worked on called 'teaserbytype'. It handles showing the teaser on node preview, and has a simpler settings interface, though it doesn't do regenerating teasers. You're welcome to use parts of this in your code :)
| Attachment | Size |
|---|---|
| teaserbytype-5.x-0.1.zip | 2.71 KB |
#1
Hi there,
I haven't got the chance to look at the code (yet), however I'll address the issue of splitting the project. The thing is that when I initially decided to make a project, the code base was small and the modules I wanted to upload were quite simple, not worthy to form a single project by themselves. Today, that's still true (mainly because I very rarely touch the code).
This project is intended as a collection of small tweaks, users can simply not activate if they don't feel the need to, or just remove the undesired .module files.
Although I agree, not everyone sees it that way, it did seem like the wiser way to go at the time.