I guess....Though it seems hardly like the stuff of dreams. Everything else in T5 is so perfect, I'd hate to see this become an eyesore somehow. (not that it ever was, but it has had it's quirks here and there ..)
I wasn't asking for Howard to implement it a particular way though, I'm perfectly happy with what he has right now. My intention was to fish for his thoughts on it and volunteer myself to implement them. T5 does need to come out at some point, I just thought the idea rang true in my head and wanted to share it. On 1/18/07, Nick Westgate <[EMAIL PROTECTED]> wrote:
In the absence of other voices, I liked Jesse earlier statement. Howard "should be allowed to proceed unmolested." ;-) It seems people are asking for criteria for when a default binding for a parameter is recommended. Some consideration should be given to documenting a few clear and simple rules for this. One could dream them up now, or wait until more components exist. My vote is for the latter. Cheers, Nick. Howard Lewis Ship wrote: > The question is ... how to proceed from here? Dump it into the trunk? > Let is simmer in the branch a bit longer? Abandon the idea and run > screaming? Feedback please! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
