- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Thu, 07 Jun 2007 11:36:23 -0700
- To: www-forms@w3.org
Aaron & all, > I don't see why an additional event is needed specific to instance > replacement. Why can't the form author just key off of the > xforms-rebuild? xforms-rebuild will not cause notification events to be sent to the controls, which is what Ryan (and myself) want, so we can detect whether the value of a control has changed. In addition, a rebuild only concerns model binds, not UI controls. The refreshing of UI controls is defined in xforms-refresh, and this is good enough as far as I am concerned: it guarantees that controls update their value and MIPs (if we can talk about MIPs for controls). > Afterall, the instance may be completely changed in structure by > more than just a submission replacing the instance. > Could also be due to an insertion at the root node level, by someone > using JS to change the instance, or a combination of these followed > by a xforms reset. All the above is absolutely correct. > Though I guess the problem here is that xforms-rebuild isn't always > generated. Like if xf:rebuild or rebuild() is done directly. Again, I don't think xforms-rebuild is the problem here. > So I think that this issue is wider than just instance replacement. You are 100% right about that ;-) We have a bigger thread in public-forms, which I hope explains things a little better: http://lists.w3.org/Archives/Public/public-forms/2007Jun/0016.html -Erik -- Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/
Received on Thursday, 7 June 2007 18:39:22 UTC