The scripts inserted by the various FX Actions are very insular – it’s hard to imagine how I would reach inside them and get them to do anything besides what they do already. I don’t believe there’s a way to take these scripts the way they are written and tell them to do anything from outside themselves. You could piggy-back on them somehow – add a classname to the elements in your group, for example, and then listen separately at the page level for a click on any element with that classname and do something else. But if those Actions do anything internally to track their state (a flag saying “I am open” or “I am hidden”), that flag would not be toggled by the external script, so the effect could get out of synch. It becomes a bit of a detective game to figure out a way to have two things happen at once when one has no idea what the other is doing.
I have looked at the way these scripts are generated within the FX Actions, and they have been written in a very modular manner. On the one hand, this makes perfect sense for the author – more maintainable, less code means less occasions for errors – but on the other, it means that the individual effects have only the most common of controls possible. There are settings in the Scriptaculous API (Application Programming Interface) that are not exposed by the Action controls; some of these could be useful, especially in combination.
That’s why if things get even a little bit complicated, my first instinct is to go right to the “metal” with the Protaculous Action. It does require that you type (or paste) some very cryptic code into its dialog, but in so doing, it exposes the geek-level interface of the full API, so you get to use all the crayons in the box.
Walter
On Dec 4, 2012, at 9:37 AM, tonzodehoo wrote:
Thanks again for this.
I’m waiting on content from the organisation who’s website I am working on.
Once I have this then I shall be making some use of this.
Its been a bit of a crash course in understanding the use of java scripts but I am excited at the possibilites.
I’ve been trying out a few scripts which are opening up a range of possibilities which sometimes raise more questions for me.
The one that comes to mind for this script is to find a way to relate it to other scripts on the page so that by closing or opening oneslider that another would be triggered open and then be able to build a sequence of such opening and closing sliders.
Any thoughts at all
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options