Re: xforms:upload updating two parts of the model

Couldn't one register a listener for DOM Mutation Events? Does any  
XForms implementation do this?

-Erik

On Feb 26, 2008, at 3:43 AM, Mark Birbeck wrote:

>
> Hi John,
>
>> Not sure, but I think you may have suggested that an xforms-value- 
>> changed
>> (XVC) will happen on the filename child element of an upload.
>> Just in case that's what you meant, the current spec does not  
>> support that
>> because the ref used in filename is not a UI binding.  Only full- 
>> blown form
>> controls receive events from the model corresponding to their UI  
>> bindings.
>>
>> It may work in an implementation that treats every ref as a UI  
>> binding, but
>> then you have odd stuff happening like XVC events going to setvalue  
>> and such.
>
> No...I'm definitely *not* saying that XVC applies to anything other
> than a form control.
>
> And that's exactly the problem!
>
> It means that for authors to register a handler that will perform some
> action whenever a particular node has changed, they have to create a
> redundant form control:
>
>  <style>
>    .xvc-event-handler { display: none; }
>  </style>
>
>  <xf:output ref="node-to-watch" class="xvc-event-handler">
>    <xf:action ev:event="xforms-value-changed">
>      ...
>    </xf;action>
>  </xf;output>
>
> Best regards,
>
> Mark
>
> -- 
>  Mark Birbeck
>
>  mark.birbeck@x-port.net | +44 (0) 20 7689 9232
>  http://www.x-port.net | http://internet-apps.blogspot.com
>
>  x-port.net Ltd. is registered in England and Wales, number 03730711
>  The registered office is at:
>
>    2nd Floor
>    Titchfield House
>    69-85 Tabernacle Street
>    London
>    EC2A 4RR
>

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/

Received on Tuesday, 26 February 2008 22:29:29 UTC