Re: The close action seems not quite right for portal scenarios

Multiple models could also be used by huge forms that want to have good 
performance.  What should happen to the form if it gets an xforms-close 
on a non-default model?  Is that model not usable anymore even if the 
other parts of the form are?  Do controls bound to instances inside the 
model go away?  What if you have an itemset pointing to the closed model 
but the select1 that contains the itemset points to an 'open' model?

I just ask that you guys keep in mind forms that are not portlets and 
what should happen to them, too.

Thanks,
--Aaron

John Boyer wrote:
> 
> The close action in XForms 1.1 dispatches xforms-close to the default 
> model.
> 
> The expected behavior is for the owning document to close down, which 
> may also close the user agent.
> 
> Somehow, it seems that we need to let the user agent be a little more 
> intelligent about the decision to close down.
> 
> The problem is that if I deliver multiple portlets, each containing an 
> XForm, and one of them invokes 'close', it seems like XHTML+XForms forms 
> will have the problem that the whole portal will shut down, not just the 
> portlet containing the one XForm that invoked the close.
> 
> Assuming that one of the most important reasons for allowing multi-model 
> forms is to support the portlet scenario (one HTML document, multiple 
> portlets with any one or several containing an XForm), then it seems 
> like we really want 'close' to indicate a model, and we will close that 
> model.  If the nearest logical container contains no more XForms models, 
> then it may decide to close down.
> 
> Comments?
> 
> John M. Boyer, Ph.D.
> STSM: Workplace Forms Architect and Researcher
> Co-Chair, W3C Forms Working Group
> Workplace, Portal and Collaboration Software
> IBM Victoria Software Lab
> E-Mail: boyerj@ca.ibm.com  http://www.ibm.com/software/
> 
> Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
>

Received on Tuesday, 31 October 2006 18:51:52 UTC