What I propose is to let this module be one main module, to activate sm2.
Then, have other submodules, which depends on the main one, to activate the formatters.

All opinions are welcome.

Comments

00110000’s picture

00110000 commented

My vote is for whatever keeps the module lightweight as possible, without over complicating things. If by having sub-modules achieves this and can keep things simple, I'm all for it.

davebv’s picture

davebv commented

I just started to separate this into small modules, the first one, (I think it's finished) is the base "soundmanager2" module.

Already working module: Soundmanager2
Features:

  • Includes the needed scripts and configuration
  • Provides a block for debugging the load of sm2.
  • In admin pages: ability to enable debug mode.
  • Change default path for sm2 additional files.
  • Provides a status with current version in reports->status, error ir soundmanager2 files are not present.
  • Will allow other modules to "require" this one to use the soundmanager2 module

todo: allow sm2 configuration tweaking in admin settings page.

TODO:
Planned extras: sm2 cck formatter module.
Maybe more to come.

davebv’s picture

davebv commented
Version: 6.x-1.x-dev » 6.x-2.x-dev
Status: Active » Needs work
davebv’s picture

davebv commented

For those who are interested, the old functionality is working now in the new version

I just started to separate this into small modules, the first one, (I think it's finished) is the base "soundmanager2" module.

See the release for details, but as I said, two modules now exist: the main module to include sm2 object (this helps for dependencies for other modules) and a basic cck formater for Filefield and audio nodereferences (in case audio module is present)

TODO:
Allow sm2 configuration tweaking in admin settings page.
Suggestions are welcome!

theohawse’s picture

theohawse commented
Status: Needs work » Closed (fixed)

13 months later I believe this is a closed issue