Only because there has been recent discussion about this Action am I actually making a public announcement (otherwise this would have happened quietly and by request).
Lightbox (the original Action meant for use with Prototype) has been updated to v0.96. The last update was in 2006.
Duplication of Proto/Scripty libraries: The action now relies on SP’ own Scriptaculous suite or Walter’s Protaculous to add the necessary libraries. I am not going to be a third to add these to the page. If you are being bitten by duplicated libraries, you are already adding the necessary code. Others will have to use another Action to add them.
Changes/Additions:
Already mentioned reliance on 3rd party Action to add JS code.
BG Opacity option in the Page Modifiers action
Added ability to perform ‘sticky’ changes when triggering the Lightbox, so the BG color can be altered for each lightbox popup within the same page (JW).
Added a couple alerts for missing images and libraries to better inform the user
Switched from a folder to a real fwaction bundle. Please manually install the Action and discard any previous version (readme.txt included)
It is currently only available as an unencoded file, which means it is for FW4/5 PRO. This also allows anyone to edit the code as they see fit. Provide me some feedback if it is needed for EXPRESS.
Notes:
I don’t intend to continue development on this Action. It is several years old and has been superseded by more modern code. I encourage the community to take over development of this Action for new features or other updates.
I do have an update in the works, though not as significant as the last. It is meant as an interim state to try to get the Suite to play nice with Prototype, and includes a couple minor bug-fixes.
Sorry, my message got chopped off, continuing… (again Mootools specific stuff below)…
BG Opacity as already mentioned (that was missing for all this time and someone finally brought the absence to my attention, Todd)
Preferred Position for Slimbox slides (another JW request), so ‘randomly’ placed images on a page can have their output slide order influenced, so it is not totally dependant on its position in the FW item hierarchy (This is just not possible in the current Proto-Lightbox Action code structure).
Tidier code output, all Slimbox links are moved to the bottom of the html instead of inline with the item
I will try for similar ‘sticky’ effects in Slimbox
However, my focus is still on at the very least notifying the user of conflicts, as right now the user is totally ignorant of these clashes and is left wondering why their page is falling apart when viewed in a browser.
I would also like to tweak all of the script building routines to use external files as templates, so that they could be ported over to Proto at some point (and vice-versa). I will always rely on others to apply the Proto/Scripty libraries as I have no interest in maintaining a second library and related files.