derernst
03-18-2011, 03:06 PM
1) Script Title: Ultimate Fade-in slideshow (v2.4)
2) Script URL (on DD): http://www.dynamicdrive.com/dynamicindex14/fadeinslideshow.htm
3) Describe problem:
I installed version 2.4 today, which is a huge enhancement compared to 1.5 I've been using before. Thanks a lot for this great script!
I'd like to propose some more configuration options for future versions:
1. backgroundcolor: '<color>'
Currently, when the first image starts fading in after page load, the background is black. It would be nice to set the background color in the properties when creating the new fadeSlideShow().
2. descappearance: {textcolor:'<color>', backgroundcolor:'<color>', alpha:<value>}
The 70% black background and white text for the description looks cool, anyway some author might want to change them.
3. pauseOnHover: true|false
This has been asked in this forum before. It would be nice to disable the pause when the slideshow is hovered without changing the source.
4. createNewElement: false|true
If set to true, the script will not touch the wrapper div, but rather create a new div inside it. This can be useful to prevent possible CSS styling of the wrapper div from being overridden by the script (currently, you can't e.g. use position:absolute). Also, it allows to apply noscript fallback without change of the structure:
<div id="myWrapper" style="position:absolute;top:50px;left:4em">
<script type="text/javascript">
new fadeSlideShow({
wrapperid: "myWrapper",
createNewElement: true,
...
});
</script>
<noscript>
<img src="my/default/image.jpg" alt="">
</noscript>
</div>
In this example, the page structure and design would be consistent whether scripting is enabled or not, while this is not the case with the current version.
BTW, I don't ask for advice on these settings, as I am capable of making such changes in the code, but thinking of later upgrades it would of course be nice to do this without touching the source code.
2) Script URL (on DD): http://www.dynamicdrive.com/dynamicindex14/fadeinslideshow.htm
3) Describe problem:
I installed version 2.4 today, which is a huge enhancement compared to 1.5 I've been using before. Thanks a lot for this great script!
I'd like to propose some more configuration options for future versions:
1. backgroundcolor: '<color>'
Currently, when the first image starts fading in after page load, the background is black. It would be nice to set the background color in the properties when creating the new fadeSlideShow().
2. descappearance: {textcolor:'<color>', backgroundcolor:'<color>', alpha:<value>}
The 70% black background and white text for the description looks cool, anyway some author might want to change them.
3. pauseOnHover: true|false
This has been asked in this forum before. It would be nice to disable the pause when the slideshow is hovered without changing the source.
4. createNewElement: false|true
If set to true, the script will not touch the wrapper div, but rather create a new div inside it. This can be useful to prevent possible CSS styling of the wrapper div from being overridden by the script (currently, you can't e.g. use position:absolute). Also, it allows to apply noscript fallback without change of the structure:
<div id="myWrapper" style="position:absolute;top:50px;left:4em">
<script type="text/javascript">
new fadeSlideShow({
wrapperid: "myWrapper",
createNewElement: true,
...
});
</script>
<noscript>
<img src="my/default/image.jpg" alt="">
</noscript>
</div>
In this example, the page structure and design would be consistent whether scripting is enabled or not, while this is not the case with the current version.
BTW, I don't ask for advice on these settings, as I am capable of making such changes in the code, but thinking of later upgrades it would of course be nice to do this without touching the source code.