When checking the code I noticed that data for individual themes is hardcoded into the Drupal.behaviors.ddblockShowHideCustomTemplateOptions function in views_slideshow_ddblock.admin.js based on some sort of naming convention that is not explained in the documentation. These data should be in the theme not in the core module.
I suggest a data array for each theme with title, description, valid input for configuration and anything else required as part of the theme (not part of the module). This way data could be set for all contributed themes (even if they do not follow your naming convention) and would allow greater flexibility in theme generation. the data array should change the options in views when the theme dropdown list is changed, or even better, change the dropdown list to a list with option buttons like the main Drupal theme page but make it collapsible to save space.
A description would be handy as currently you do not know what pager, etc is shown until you have set up the view. A screenshot would also help.
Comments
Comment #1
ppblaauw commentedYes, the naming convention is ugly, but did not have an alternative.
Your suggestions is great. Having an array with settings in the theme would be a big improvement in flexibility.
I added the screenshots of the themes at the download page, but it would be nice when the theme screenshot is show when the theme is chosen from the dropdown.
Do you have code how to implement both features?
Comment #2
SweeneyTodd commentedI do not have any code at present but will look into it. My coding may not be up to the task as I am a novice the php / Drupal development.
I have some time free so I am going to look at some of the issues in your code to try to help with the module (that's one of the reasons why you are getting more comments from me at the moment).
Use my contact form to get in touch and we can discuss where I can best use my effort and make sure I do not duplicate effort put in by you.