I've been thinking about this too; including a deprecation service that would log the deprecation warnings ... but just once, so you don't get flooded.
On 5/14/05, Jamie Orchard-Hays <[EMAIL PROTECTED]> wrote: > > I like this idea. It would definitely be useful. > > Jamie > > > On May 14, 2005, at 5:15 AM, Richard Lewis-Shell wrote: > > > 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] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
