On 21/05/2014 13:07, Walter Lee Davis wrote:
I get it, that makes sense. So the fwDocument (which represents the entire document, all pages) is there within the context of the single page while the Action is running, allowing you to look at other pages, but it doesn’t persist after that page is completed and torn down.
This gist looks fascinating. I didn’t know you could build up a fwParameters element like that, without declaring it as an in the preamble of the Action.
Well, the PageList parameter is declared in the Action header, it just doesn’t have any content until the callbacks start doing stuff with it. It was declared as an action-number and an action-string (??!) before I eventually got it right as an action-text
Now for future API goodness, we need to be able to go the other way, and dynamically create an interface element as needed, so we won’t need -60 versions of Actions for people whose sites “go to 21”. I’ve simulated this before: look at my Protaculous 2 action, which seems to let you add a variable number of external libraries, but is really just un-hiding the next one the moment you add one. That has an upward limit, based on how bored I got adding initially-hidden groups of elements.
Yeah, this is a long-standing problem internally as well. I believe the Exhibeo Action has several hundred initially hidden parameters I would like to be able to say that this is something that is easy to implement, and be done soon, but unfortunately it’s somewhat foundational in the Action machinery. I’ve had a look at doing this before, but there’s a vast amount of code reliant on Actions having fixed numbers of parameters.
actionsdev mailing list
Update your subscriptions at: