I have created a patch that loads the skin options by reading directory names from the skins folder within the module's folder. This is so that skin creation is now a simple matter of creating a folder with a skins.css file. It eliminates the need to modify actual project code to implement a custom skin. This will also greatly simplify upgrading the project code to latter versions.
This patch removes the "custom" skin option when setting up the view, but honestly, that option really didn't do anything anyway.
Due to local conflicts when trying to use the jcarousel module, I am unable to move to the 6.x-2.x branch and apply or test any fixes there but, having taken a quick glance at the 6-2 code, I believe much of this fix should be portable.
| Comment | File | Size | Author |
|---|---|---|---|
| viewscarousel.patch | 2.36 KB | sjpatrick |
Comments
Comment #1
mfer commentedThe 1.x version of the module is by design the way it is. But, there are plans for the future of jcarousel in Drupal. Having the ability to provide skins will be one of them. This will just not be going in the 1.x or 2.x versions of this module.