- From: Adam Retter <adam.retter@devon.gov.uk>
- Date: Tue, 30 Oct 2007 10:38:50 +0000
- To: www-forms@w3.org
Hi chaps, I have just digested and hopefully understood the discussion that you have been having with my colleague Robert Walpole and his need for a non-destructive xforms:copy. I recently implemented xforms:copy in Chiba to the XForms 1.0 specification, and am considering now modifying it to provide the functionality that Rob requires. If I understand correctly - the proposal for XForms 1.1 is to change the default behaviour of xforms:select and xforms:select1 from destructive to non-destructive with appropriate range out-of-bound behaviour? Now whilst we have a use case for this and it is indeed desirable, I am slightly concerned that we are changing the default behaviour and that this could effect many people. I think perhaps Aaron Reed is correct by suggesting that the default behaviour should remain destructive and an attribute @selection be added to allow for non-destructive behaviour. I am looking to implement the recommendation this week if possible. Has there been any further thought, on whether the default behaviour should change or whether it should be configurable through an attribute? Thanks -- Adam Retter Principal Developer Devon Portal Project County Hall Topsham Road Exeter Devon EX2 4QD t: +44 (0)1392 38 3683 f: +44 (0)1392 38 2966 e: adam.retter@devon.gov.uk http://www.devonline.gov.uk
Received on Wednesday, 31 October 2007 00:41:52 UTC