On Fri, Feb 17, 2012 at 9:35 AM, Kevin Wright <[email protected]>wrote:
> My only critique is that I prefer scalate's jade templating language over > play's own templates. But there's a module available for that, so it's > really not a very big complaint :) This is another important aspect for a web framework, in my opinion: being template technology neutral. There are many, many ways to generate content with templates. First the back-end/front-end dichotomy. On the back-end, you have Freemarker, maybe Velocity (kinda abandoned I think?), Scalatra and then the web frameworks' own templating mechanisms. On the front-end, you have another embarrassing of riches, such as Mustache or Handlebars. Going even further, you can reconfigure your CSS with on-the-fly technologies such as Less, or generate them statically and including them the normal way. And of course, the web framework must also be at least Javascript neutral and ideally, offer some kind of integration with mainstream Javascript technologies such as jQuery. -- Cédric -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
