In the old code tabSet javascript code, we would hook into the tabSet's tab change listener's submit listener, to do some processing after the server had rendered the new tab content. So we'd have both the old tab and the new tab available for doing animations on. With the new code, it uses an ondomready call that defers the processing of the new tab contents until after the submit listener would have been invoked. This means that we don't have that simple place to access both tabs for animations. Possibly we'll need to do the animation for hiding the old tab, and then do the submit, and then do the animation for showing the new tab.

Need to integrate the new ace:animations (based on jquery effects) with ace:tabSet.

This can take the form of adding showEffect/hideEffect attributes to the ace:tabSet (for showing/hiding the tabpane when selected/deselected). Also add showEffectLength/hideEffectLength attributes like we have with ace:tooltip.