Joseph,
I'd offer two suggestions:
1) You'll save yourself a lot of trouble if you use an approach
similar to @Border and have your table form "wrap" an edit area. Then you
can embed different edit areas as you see fit and keep the table in place.
Check out the doc on @Border to give you an idea of how to do it, although
you don't have to do it with an @Border component.
2) You can usually get a more responsive UI if, instead of each tab
being a different form, each tab is a different div and you just hide/unhide
them (a client side operation) in response to user activity. Robert was
going to package up a Tab Control of mine that did just that when he has
some spare time, so you might want to touch base with him and see if he's
gotten that put together yet; it may help you out some.
--- Pat
> -----Original Message-----
> From: Joseph Hannon [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 30, 2005 7:21 AM
> To: [email protected]
> Subject: Multi-page form design question
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
