Deprecating components

[Richard Lewis-Shell]

Hi,
I am thinking it would be useful to add support to Tapestry for 
deprecating components, so that we can provide a clear migration path 
for changing components.  It can imagine it would be useful to be able 
to deprecate an entire component and/or individual component parameters, 
and have Tapestry display a warning when such components/parameters are 
constructed.  It would probably be desirable to be able to disable those 
warning messages, perhaps via a system property.  Off the top of my 
head, it might look like this:

Foo.jwc:
<component-specification ...>
   <deprecated message="Use the simpler Bar component instead of Foo"/>
   <parameter name="something">
       <deprecated message="Use somethingElse parameter"/>
...
e.g. there is a thread on the -user list at the moment about merging 
Insert and InsertText.  If deemed a good idea, it would be nice to 
deprecate the InsertText component, leaving it in Tapestry 4, and 
removing it from the next significant release.

Any thoughts?
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]