You can add it to JIRA, but in 5.4, Tapestry is getting out of the client-side animation business.
The pattern in 5.4 is that components will fire DOM events describing what's going on and, if you want, you can have a listener on the element, or a global listener on the body, provide the necessary UI animation. I've found in most applications that I've written that I ended up turning off the animations anyway. On Wed, Aug 15, 2012 at 9:59 AM, Dusko Jovanovski <[email protected]> wrote: > I like the zone component > symbols, ComponentParameterConstants.ZONE_SHOW_METHOD = > "tapestry.components.zone_show_method" > and ComponentParameterConstants.ZONE_UPDATE_METHOD = > "tapestry.components.zone_update_method", but I would expect the > ProgressiveDisplay to honor the same symbol as the Zone component, or > optionally another separate symbol for the update parameter. > > Dev list, JIRA worthy or expected behaviour? -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
