I'm about to install and use Bones again on a new site, it occurred to me that it might be useful to adopt the libraries directory as a place to store the YAML parser following where the WYSIWYG module looks for the FCK editor or TinyMCE.

We could adapt the code from that module (around lines 800 > 900) or implement the Libraries API.

I like this idea because when I update a module with DRUSH I should not need to hunt around for the library, example: When I update the original FCKEditor module DRUSH makes a backup of the current module and installs the latest version but then you need to go to the backed up module and move the FCKEditor files back into the module again. Which makes DRUSH in these cases less advantageous.

If I get time I'll try and write a patch. What do you think of this idea?

Comments

joachim’s picture

joachim commented

+1

usonian’s picture

usonian commented
Assigned: Unassigned » usonian

Having to keep track of external libraries for modules has always been a pain - as much as I've always wanted to keep this a standalone module to minimize the amount of stuff people have to download, the libraries API is pretty compelling. I'll take a look.