Possibly also a series of tabbed panes or a wizard. Tabbed panes and
wizard-like dialogs are becoming popular in JSF. There's also the
popup windows that you were talking about below as well.
On 1/11/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
> Answering my own question ... Assuming the view layer handles all the
> validation on each POST before updating the model, there is one
> general scenario where nesting is useful: when you need an ability to
> cancel two or more screens of local changes without reverting all of
> the local changes. It is more common in rich GUI (dialogs that pop
> their own dialogs) than web, but I've seen it quite a few times in
> internal business web applications.
>
> Still have a feeling that I am missing something, but at least I've
> identified one realistic scenario...
>
> Andrus
>
>
> On Jan 11, 2006, at 3:11 PM, Andrus Adamchik wrote:
>
> > I am working on the nested DC feature. I started by creating a demo
> > application with Click front-end. What I discovered though is that
> > since Click provides another layer of objects (UI stateful widgets)
> > in front of Cayenne-based model, I can't come up with a scenario
> > where a nested context is needed (as opposed to say a peer context)!
> >
> > The need for it was clear in WebObjects when object state was
> > dynamically bound to the page, so you'd have to prepare your object
> > model on GET without any guarantee that the matching POST would
> > happen.
> >
> > But if you use frameworks like Click (and actually Struts, with
> > ActionBean playing the "front row buffer" role), where does it fit
> > here?
> >
> > I am probably just having a bad day, as I am sure there were a few
> > important scenarios that I am missing now.
> >
> > Andrus
> >
> >
>
>
This archive was generated by hypermail 2.0.0 : Wed Jan 11 2006 - 17:52:44 EST