RE: selection="open" attribute on a selectOne element

Greetings, if you are using as old a version of the spec as you indicate 
you may not realise that in the latest version you are allowed to have 
multiple instance elements in a single model. So yes, two instances, but 
that no longer requires two models.

Regards, Roland



"Robert Bull" <rob.bull@blackdog.co.uk> 
Sent by: www-forms-request@w3.org
22/10/2004 15:12
Please respond to
rob.bull


To
<www-forms@w3.org>
cc

Subject
RE: selection="open" attribute on a selectOne element






Mark,
 
what is the advantage of using a single model in this scenario. Surely 
allowing the select1 and the itemset to utilise different models permits 
the gathering of data from multiple sources to be serialised for one 
submission? How could that be achieved if the select1 and the itemset have 
to be from one model?
 
Using different models seems to be supported in FormsPlayer 1, and gives a 
very flexible architecture.
 
Regards
 
Rob
 
****************************************************
*  This e-mail is for the intended recipient only, *
*  its contents and the content of any attachments *
*  is copyright material belonging to HoT Training *
*  and Consultancy Ltd, and all information herein *
*  should be treated as Company Confidential       *
**************************************************** 
-----Original Message-----
From: www-forms-request@w3.org [mailto:www-forms-request@w3.org]On Behalf 
Of Durnell, Carryl
Sent: 22 October 2004 15:01
To: Mark Birbeck
Cc: www-forms@w3.org
Subject: RE: selection="open" attribute on a selectOne element

Thanks for that - I'll look into changing it to only use one model if I 
can, as I can't see anything else wrong with it.

From: Mark Birbeck [mailto:mark.birbeck@x-port.net] 
Sent: 21 October 2004 17:39
To: 'Durnell, Carryl'
Cc: www-forms@w3.org
Subject: RE: selection="open" attribute on a selectOne element

Carryl,
 
Wow! I believe that's now a collectors' item ;)
 
But on your general point, yes @selection="open" should work the way you 
describe.
 
Mark
 
PS There is some ambiguity as to whether you should be allowed to use a 
different model on the xf:itemset than on the xf:select1. The consensus at 
the moment is that they should not be from different models, so watch out 
there, too.
 
Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/

Download our XForms processor from
http://www.formsPlayer.com/ 
-----Original Message-----
From: Durnell, Carryl [mailto:Carryl.Durnell@logicacmg.com] 
Sent: 21 October 2004 16:33
To: Mark Birbeck
Cc: www-forms@w3.org
Subject: RE: selection="open" attribute on a selectOne element

Hi Mark,
 
We are using quite an old implementation - the "Working Draft 18 January 
2002" version, which would explain the use of deprecated tags.  However, 
this version still describes the use of this attribute, so I thought it 
should work!
 
Cheers,
Carryl

From: Mark Birbeck [mailto:mark.birbeck@x-port.net] 
Sent: 21 October 2004 16:24
To: 'Durnell, Carryl'
Cc: www-forms@w3.org
Subject: RE: selection="open" attribute on a selectOne element

Carryl,
 
<selectOne> had its name changed a very long time ago to <select1>, and 
<caption> is now <label> ... so I think the first question is what 
implementation are you using?
 
Regards,
 
Mark
 
Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/

Download our XForms processor from
http://www.formsPlayer.com/ 
-----Original Message-----
From: www-forms-request@w3.org [mailto:www-forms-request@w3.org] On Behalf 
Of Durnell, Carryl
Sent: 21 October 2004 15:59
To: www-forms@w3.org
Subject: selection="open" attribute on a selectOne element

Hi,
 
I'm trying to get a field that shows a value pulled from the database, but 
then allows the user to either accept this value, or input a new value - I 
had understood this was possible using the selection="open" attribute on a 
selectOne element, but can't get it to work.  The field displays the value 
pulled from the database, but doesn't allow me to input an alternative 
value.
 
It could be that I am merely missing some code to handle the input 
correctly, or something else, I'm not sure - see code snippet below:
 
       <xf:selectOne selectUI="menu" ref="/data/xmit_num" model="pagedata" 
id="LPStoPSXmitNum" selection="open">
        <xf:itemset nodeset="//configset/configitem" 
model="existingconfig">
         <xf:caption ref="lps_to_ps_xmit_num"/>
         <xf:value ref="lps_to_ps_xmit_num"/>
        </xf:itemset>
       </xf:selectOne>
 
Any and all advice gratefully received!
Carryl
Carryl Durnell
FASTWIRE Consultant
____________________________
LogicaCMG
75 Hampstead Rd., Stephenson House
London
UK
T: +44 20 7446 1775 (direct)
F: +44 20 7446 1777
E: Carryl.Durnell@logicacmg.com 
www.logicacmg.com
 

This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an 
intended recipient then please promptly delete this e-mail and any 
attachment and all copies and inform the sender. Thank you.

This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an 
intended recipient then please promptly delete this e-mail and any 
attachment and all copies and inform the sender. Thank you.

This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an 
intended recipient then please promptly delete this e-mail and any 
attachment and all copies and inform the sender. Thank you.