> That way the buttons SHOULD all have
> the same name for each iteration, and
> different one for the next one etc..
> That was the thinking behind it.
Thanks for your quick and helpful response.
That is yet another reasonable interpretation of how
to map the collection to radio buttons.
There many reasonable ways one might want
to map the collection. I think is important that
1) the tag supports the reasonable mappings (e.g., how do
I do what I wanted to do using the html:radio tag)
2) since there are many possible mappings and how to do
it is NOT AT ALL INTUITIVE there needs to be some
decent documentation and examples.
I think it would be good to start this process by defining some
of the mappings it should support. This would include mapping
of the collection information to the button specs and the
mapping of the button selection back to the collection (or
something else - e.g., makes sense to me to allow mapping of the
selected value to a single variable). David Karr seems to have
some good suggestions.
Frank Lawlor
Athens Group, Inc.
(512) 345-0600 x151
Athens Group, an employee-owned consulting firm integrating technology
strategy and software solutions.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
