You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Chris Nelson <cn...@yahoo.com> on 2005/02/18 04:35:47 UTC

Extending the Palette component

All,

In working on Trails I have come to a point where I
really need a component which will let you reorder and
remove things from a list.  In looking thru the
Tapestry code (3.0) for the Palette component, it
looks like a reasonable approach to make a component
something like a one column palette, since in my case
I will only have one list.  However, several of the
methods I would want to override are private methods
on Palette.  So my question is, would it be reasonable
for me to think about refactoring the Palette
component?  The other option would be to cut and paste
code, which I always hate to do.  Are there test cases
for this component?  Are there things in 3.1 which
make it easier to unit test components?  Has anybody
already done a component like this and can recommend a
better solution?

Thanks in advance,

Chris Nelson




		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org