-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
Just taking a look at the Selection and Option components within Tapestry.
I am aware that for single-selection, a PropertySelection component is
probably more appropriate.
Doing a grep through the examples directory, I did not come up with anything
that uses a Select component, so here goes:
I assume that Selection and Option should really be combined with a Foreach,
e.g:
<form ...>
<span jwcid="select"/>
<span jwcid="foreachThing">
<span jwcid="option"/>
</span>
</span>
</form>
where foreachThing is bound to some component that the option can render.
Note: this is a complete guess at it's usage - I could be entirely wrong
here. I imagine that the implementing .java file would maintain both a
list of objects forming the selection criteria, as well as those that are
currently 'selected', which would allow the 'option' component above to be
rendered correctly at each iteration.
Is this kind of how Selection / Option are intended to be used? Or am I
heading in the wrong direction?
Cheers,
- --
Neil
(BTW: If you see weird text surrounding the message and you don't know what it
is, don't worry, it's just my public PGP signature).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9a7oRLXcfQF3yrNoRAuCqAKCtFwwA4tHTRj33m0VKsgec1AFznQCfZVTG
mK7mWK7bdpB5EKLqzqfGtj4=
=UahZ
-----END PGP SIGNATURE-----
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
