W3C home > Mailing lists > Public > public-forms@w3.org > January 2008

Pretty cool talk today; how about switch *inside* select1/select

From: T.V Raman <raman@google.com>
Date: Thu, 31 Jan 2008 15:00:50 -0800
Message-ID: <18338.21282.237371.398388@retriever.corp.google.com>
To: boyerj@ca.ibm.com
Cc: public-forms@w3.org

John, I found the minutes interesting reading.

going back to how we designed repeat,
and then enhanced select/select1 with itemset to do select
controls that picked their choices out of a model, here is a
design pattern that would mimic that direction:

Today, we have:

select/select1 which take either of:

a set of statically authored choices that appear in item/label

A set of dynamic choices that come from the runtime authored via

Today we have so far:

A switch with multiple case elements where one is specifying the
cases in the UI layer:
The analogous extension would be to allow a 
<caseset> element inside switch (I dislike the name but all names
deserve to be converted to opaque digits anyway;-)

Without prejudicing the design based on the name therefore:

A direction to proceed would be to extend switch to cover the
dynamic case just as we extended select/select1 ---

Finally to the teleconf discussion about group vs cae, I've long
felt that case is just syntactic sugar (albeit useful sugar) for group.

John Boyer writes:

Best Regards,

Title:  Research Scientist      
Email:  raman@google.com
WWW:    http://emacspeak.sf.net/raman/
Google: tv+raman 
GTalk:  raman@google.com, tv.raman.tv@gmail.com
PGP:    http://emacspeak.sf.net/raman/raman-almaden.asc
Received on Thursday, 31 January 2008 23:01:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:13:55 UTC