At Howard's suggestion, I've started thinking about reimplementing the
current PopLink as a "wrapper" to the existing dynamic Tapestry link types,
something along the lines of Rollover.
A couple of issues have cropped up. Someone has suggested/requested "Pop"
functionality for Buttons, not just Links, and that obviously makes sense.
Rollover is used by wrapping the Rollover with a Link, but a Button can't
wrap anything. So this suggests that the Pop should wrap the control (Link,
Button, etc), rather than be wrapped by it. Like this:
<span jwcid="detailPop">
<span jwcid="aLink"/>
</span>
Also, in my mind (YMMV) the markup is more intuitive this way than the other
way around.
If there is a single Pop component that can wrap disparate components, like
Link, Button, etc, there is the issue of how to provide type-safety for the
thing that gets wrapped. The Pop could look at the type of the thing that it
wraps and check it against a laundry list of valid taypes. Obviously this is
a pretty clunky design. The prettier solution would be to introduce a
"tagging" interface "Popable" that any wrapped component would have to
implement.
Howard, let me know if this makes sense.
Joseph Panico
[EMAIL PROTECTED]
_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
- [Tapestry-developer] Poplink Joseph Panico
- [Tapestry-developer] Poplink Joseph Panico
- Re: [Tapestry-developer] Poplink hlship
- Re: [Tapestry-developer] Poplink Howard M. Lewis Ship
