I'm currently investigating whether Scala-support would require/suggest more changes than that. But Scala seems to be interoperable to an amazing degree. I'm not sure whether this kind of property-support alone would warrant the overhead of an own plugin. I'd like the idea very much, if we'd come up with whole bunch of Scala-goodies (re-usable traits for components, Scala-specific support for SelectionModels and the like).
By the way, I think jumping the Scala bandwagon a bit would be an easy win publicity-wise for Tapestry. 2007/6/25, Howard Lewis Ship <[EMAIL PROTECTED]>:
Ultimately, a pluggable architecture for deducing the properties of a class could be implemented. That would allow scala support to be a plugin. On 6/25/07, Massimo Lusetti <[EMAIL PROTECTED]> wrote: > On 6/24/07, Marcus Schulte <[EMAIL PROTECTED]> wrote: > > > I think, it would be nice, if the prop-binding, especially in T5, would > > support the scala flavour of getter and setter methods. That would mean > > that, as an alternative to int getX(), setX(int x), int x() and x_$eq(int > > x), would be recognised as valid accessors to the property "x". > > What do you think? > > If it is documented well (not causing question for why this and that > do the job while the other dont) this would be a nice nice feature. > > -- > 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]
-- Marcus Schulte http://marcus-schulte.blogspot.com
