I ran into this many times when I was first learning Tapestry as well. I still do occasionally: it would be nice to have a combination of optional cruft detection, plus MB' s validator :-)
On Tuesday, September 10, 2002, at 10:51 AM, Holger Hoffst�tte wrote: >> Phil Surette wrote: >> (snip) >> wouldn't care)? It's a nice feature to be able to be able to >> automatically detect cruft when you're in cleanup mode, but when >> you're >> in development mode you probably want the framework to be more >> tolerant >> of cruft. > > Agreed. +1 for optional! > > Holger > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
