I see. Well, I doubt that it would make sense to add to the core of Velocity support for these types, since it would imply adding a runtime dependency for Scala.
However, most of these look like things that could be accomplished using a custom uberspector, and since Velocity is becoming more modular with the transition to Maven, it would be possible to include a special submodule for better Scala support, which could then be used by anybody working with Scala. On 06/01/2013 09:30 PM, Stephen Samuel (Sam) wrote: > Off top of my head, these are ones I've already added in my local build. > > - If an Option is a None then it should not render (ie like null) > - Scala collections - be able to use #foreach on Scala iterables > - Detect scala properties without needing to use () or declare member > variables with @BeanProperty. > > This does introduce a new dependency on the scala library, which is why you > might want to do this as some kind of add on release or separate fork. > > I think this is very useful for people who are using velocity in Scala > because they are unable or unwilling to use something like Scalate. > > > On 1 June 2013 22:54, Sergiu Dumitriu <sergiu.dumit...@gmail.com> wrote: > >> On 05/31/2013 05:23 PM, Stephen Samuel (Sam) wrote: >>> Is there any interest in extending Velocity (separate dependency perhaps) >>> to support standard Scala types such as Option and Scala collections ? >>> >> >> Can you be more specific? What kind of support are you interested in? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
