Some new Ajax Frameworks stuff:
<wo:AjaxFunctionLink type = "update">update</wo:AjaxFunctonLink>
calls "update" function for the AjaxUpdateContainer this is inside of
<wo:AjaxFunctionLink type = "edit">edit</wo:AjaxFunctonLink>
calls "start edit" function for the AjaxInPlace this is inside of
<wo:AjaxFunctionLink type = "save">save</wo:AjaxFunctonLink>
calls "save" function for the AjaxInPlace this is inside of
<wo:AjaxFunctionLink type = "cancel">cancel</wo:AjaxFunctonLink>
calls "cancel" function for the AjaxInPlace this is inside of
All of these also have an optional updateContainerID if the links
appear outside of the container. These are different than
generated for each of these operations rather than actually
generating a new Ajax.Updater like AjaxUpdateLink would. For
instance, this would call someContainerUpdate() .
There's an AjaxFunctionButton also that works the same way but with a
value = "text in button" binding.
In the previous AjaxBusyIndicator it would toggle a div to display.
If you add the new "busyClass", this changes the behavior to instead
toggle the given class name on the element that is being updated.
For instance, if you have an AjaxUpdateContainer, with busyClass =
"busy" bound, when the update container updates, it has the class
"busy" added to its div. This allows you to do per-div busy
animations. For instance, if you defined:
background-position: right top;
You would get a spinner in the upper right of every div that updates
that is localized to the update rather than a single top level busy
AjaxHighlight Default Hidden
AjaxHighlight has a new "hidden = 'true'" binding you can add, which
makes it more useful to for setting effects that presume to start
hidden. For instance:
<wo:AjaxHighlight value = "$repetitionBlogPost" effect =
"BlindDown" hidden = "$true">...</wo:AjaxHighlight>
If this object is "highlighting", it will start hidden and then blind
down (instead of doing the yellow flash).
Get latest updates about Open Source Projects, Conferences and News.