Instead of a page for the confirm dialog, why not use an eventlink w/ a "confirm" mixin?
On Wed, Aug 17, 2011 at 12:05 AM, ixcoatl <ixcoatl_pe...@yahoo.com.mx>wrote: > Everything worked as you said, t:pagelink instead of t:actionlink, and > @InjectPage instead of @Inject. > > The silly part is that I had used both techniques before, but I got > confused > up with the names and usages of each one. > > Regarding to Thiago's questions, > > "I guess you're using a structure that isn't common... " > > Yes, I know, my first idea was to build all the functionality of > creating/updating/destroying users in the same page, filtering parameters > to > decide what info to show and what actions to take. Then I realize that it > was easier to just create pages for every task, and then I was stuck trying > to jump to the other pages :S. > > "Why do you need a page for removing users? Isn't an event enough? ..." > > The delete page was intended to show a confirm dialog so the user would > know > he was removing the user. > > Thank you for your quick response and documentation pointers, I have quite > a > bit to read and maybe a lot to ask :D. > > Right now I'm back on the road. > > Cheers! > > > > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Jumping-to-a-new-page-tp4706239p4706851.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
