I'll get to it tomorrow. I have to admit that I've never found a reason to use the majority of page related methods. (pageBeginRender being the exception). Hivemind has always existed since I've known tapestry so intercepting services/etc has always been my preferred approach for things like this.
On 7/25/06, Nick Westgate <[EMAIL PROTECTED]> wrote:
Guess I'm +0 this. I look forward to comments from the devs. Looking at the naming of things it's obvious (with hindsight) that the pageBeginRender name doesn't quite fit with the rewind. Sure it's a kind of virtual render, but the intended use of the event is not very clear. pageInitialise (actually, should be -ize) is probably not a good name either. Given activateExternalPage, perhaps pageActivate? Bah. The hardest part of programming. ;-) Hopefully Howard nails this in T5! Cheers, Nick. Henri Dupre wrote: > On 7/25/06, Nick Westgate <[EMAIL PROTECTED]> wrote: > >> The other option is another listener, but it seems a bit superfluous: >> >> pageAttached >> pageValidate - check user is allowed to access page >> activateExternalPage - setup here - but only for external pages >> +++ pageInitialise - setup here - not called for rewind? > > > I like this option... It makes sense to me and looks better than > pageBeginRender... > > pageBeginRender - setup here - but check for rewind > >> pageEndRender >> pageDetached > > > Cheers, > > Henri. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
