You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Nick Westgate (JIRA)" <ta...@jakarta.apache.org> on 2005/07/16 06:01:11 UTC
[jira] Commented: (TAPESTRY-400) LinkSubmit and Rollover should be able to play together.
[ http://issues.apache.org/jira/browse/TAPESTRY-400?page=comments#action_12315967 ]
Nick Westgate commented on TAPESTRY-400:
----------------------------------------
I decided to implement this recently, too, and will release it soon in a new version of LinkSubmitOrSpan on Tassel.
Tapestry's runtime enhancement of abstract methods makes it difficult to mix this functionality by composition. Since implementing IFormComponent is simpler than implementing ILinkComponent, I created a new AbstractFormLinkComponent class derived from AbstractLinkComponent, copying and pasting the few simple methods necessary. This meant just a few small changes were required to LinkSubmit.
This is still ugly, but works. It would be great if the component framework divided up the internal component rendering process in a way that made rolling new components easier. I plan to look into that soon, though my java experience is limited (1 year, vs 8+ years of C++).
> LinkSubmit and Rollover should be able to play together.
> --------------------------------------------------------
>
> Key: TAPESTRY-400
> URL: http://issues.apache.org/jira/browse/TAPESTRY-400
> Project: Tapestry
> Type: Improvement
> Components: Framework
> Versions: 4.0, 3.0.3
> Reporter: Geoff Longman
> Priority: Minor
>
> Rollover works with ILinkComponents like DirectLink to provide, well, rollover image functionality.
> In the project I'm working there is a requirement to use LinkSubmit with rollover images. But, Rollover expects an ILinkComponent and LinkSubmit is a IFormComponent and not an ILinkComponent.
> I have a kludge to make this work but it is suboptimal and not sure if the powers that be here will allow me to share. The kludge is to create my own LinkSubmit with a modified copy of Tapestry's LinkSubmit source. The modification entails making LinkSubmit also implement ILinkComponent. Anyways, there is probably a better way to do it .
> Not sure when I can come back and resolve it so I'm adding this issue to prevent it being forgotten.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org