I think it's good to use some AJAX components from Tacos library to do better UI. It's easy to make conditional blocks, then refresh them asynchronous on the server and finally post it back to page. Everything without page reloading.
2005/8/30, Darío Vasconcelos <[EMAIL PROTECTED]>: > For complicated input sequences that would use several pages > otherwise, I prefer using only one page and creating a rather > complicated .html with lots of conditionals that display the part of > the process that corresponds to the "state" of the page. This helps me > wiring complicated logic -when one form would have several different > exit and "back" options- and keep all my logic in the same .java. > Additionally, this makes it somewhat easier to create stateless pages > -by keeping track of properties- and definitely saves you a lot of > typing (especially creating all those abstract methods) > > Of course, I do all this while trying hard to componentize the .html, > so it doesn't grow too large. > > Regards, > > > Dario > > On 8/30/05, Joseph Hannon <[EMAIL PROTECTED]> wrote: > > I am beginning to design a multi-page form piece in my application and would > > like input on ways to do this in Tapestry and if there is already built in > > stuff I can use or add. > > > > The top part of each page will have a contrib:table displaying the same > > shared List of objects across all pages. The bottom part of each page will > > be a tab control I will write, each tab containing it's own form of > > controls. Clicking through the tabs will show each tab's form contents based > > on the item selected in the table. Staying on a tab and changing the > > selection in the table will update the tab form with the new table object's > > attributes. I was thinking of creating a template, class, and page for each > > tab so that all would not be in a single template, class, page making it > > potentially large. I am also thinking of making the top part of the pages > > (contrib:table) a component so that I don't duplicate code and get some > > reuse. > > > > Does this sound like a reasonable approach? Does it make sense when clicking > > a tab to route to a separate class for that tab (each tab having it's own > > class)? Have you done this and have experiences you would share? Is there > > some way to do this that makes sense in Tapestry or is there something I can > > grab and add to the mix? Would you handle this situation differently? I > > would like to hear what you think. > > > > Thanks! > > Joseph > > > > > > > -- > I have enough money to last me the rest of my life, unless I buy something. > Jackie Mason > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
