I agree, or it could be done as a branch. I'm not sure how this could be done as an add-on.
The existing components would need to change, to provide a kind of "configurator" object to invoke setFoo() and bindBar() on. On 2/2/07, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
On 2/2/07, Kent Tong <[EMAIL PROTECTED]> wrote: > There haven't been many users expressing their ideas about this. For > those that have, it's about a 50% split. As I think this is a very > useful feature, I'd like to find a place to implement it. Should I > put it into a branch, or a separate 3rd party add-on project hosted > outside Apache? Even if i find my way find with all-binding, why host it outside apache? Couldn't it be a subproject for Tapestry itself? -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
