Maybe it needs a context parameter, and it could fire an event before rendering its body. It even could render the response from the event (if any) instead of its body. What do you think?
On Fri, Feb 27, 2009 at 5:17 AM, Andy Pahne <andy.pa...@googlemail.com> wrote: > > > Forget about my previous comment. I just had to persist some properties and > it worked. Even in loops... > > Thanks Howard, nice addition! > > Andy > > Andy Pahne schrieb: >> >> Very recently a new component arrived: ProgressiveDisplay. Very nice and >> very useful. >> >> See >> http://tapestry.formos.com/nightly/tapestry5/tapestry-core/ref/org/apache/tapestry5/corelib/components/ProgressiveDisplay.html >> >> >> I tried a very basic example, and it works. Still, I don't know how to do >> anything really useful with it. >> >> >> My real world example: >> >> <t:ProgressiveDisplay >> initial="block:checkingAvailability" >> class="progressiveDisplay"> >> >> ${hotel.id} >> <t:block id="checkingAvailability"> >> Availability of ${hotel.name} is checked >> </t:block> >> >> </t:ProgressiveDisplay> >> >> >> The initial block is displayed correctly, but the progressive display >> fails, because "property hotel is null within property expression hotel.id". >> >> >> What do I have to do in order to pass some kind of context? >> >> >> Thanks, >> Andy >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
