Comments on: Building the ideal web application template engine

By: Anonymous

Anonymous — Fri, 13 Jan 2012 02:19:00 +0000

Shameless plug to my own library: http://code.google.com/p/jatl/ Which is template-less in perhaps a different way then you mean

By: New features and extensions in Mustache.java | java rants

New features and extensions in Mustache.java | java rants — Sun, 09 Oct 2011 23:30:48 +0000

[...] extensions in Mustache.java Posted on October 9, 2011 by Sam PullaraAlmost a year and a half ago I talked about my implementation of mustache, which I call mustache.java. Since then, we used it to develop [...]

By: Jawher Moussa

Jawher Moussa — Sat, 05 Mar 2011 21:13:00 +0000

Hi there,

I’m a bit late to the party I know.

I too am very interested in templating in general, and wasn’t very happy with the existing solutions out there. I found Mustache to be a bit better than the rest. I’ve layed out my ()detailed opinions in a blog post over here: http://jawher.wordpress.com/2011/01/06/on-templating-and-a-shameless-plug-of-moulder/

I’ve also went the extra mile and created a templating library that isn’t just JSP with nicer tag names which I called Moulder and made it available under the MIT license in Github: https://github.com/jawher/moulder-j

Here’s another post that shows Moulder in action: http://jawher.wordpress.com/2011/03/03/moulder-in-action/

Sorry for the multitude of links: I’m not just trying to spam your blog, but I’d be very interested in what you think about Moulder’s approach.

Cheers !

By: Peter

Peter — Sun, 10 Oct 2010 15:30:00 +0000

The problem with templating is that a new developer is required to learn it and it is another lib which could have bugs. Another big problem is the ‘partial’ thing which was really really annoying for me the last time I did RoR. So, I think “Composable components, not monolithic pages” is very hard to achieve with them …

There are 3 template-less solutions in the Java world I am aware of:
Apache wicket where you code with Java and html,

vaadin (via gwt) where you code in pure Java,

and an agpl project itsnat (through its license I don’t know much of it)

By: Ggg

Ggg — Mon, 30 Aug 2010 09:40:00 +0000

come on guys!nwe need logic everywhere… how could we chose less-logic stuff…. are we moron?

By: Koalillo

Koalillo — Fri, 18 Jun 2010 03:32:56 +0000

Cool! That's a very important feature for me!

By: spullara

spullara — Fri, 18 Jun 2010 03:28:19 +0000

Just realized you can already do this in mustache.java. You can pass in your own superclass for generated Mustache classes and override the partial() resolution method.

By: spullara

spullara — Fri, 18 Jun 2010 02:54:14 +0000

1. That seems very reasonable. I was actually planning on doing something like this anyway, thanks for the reminder.
2. Yeah, jsp tag-like behavior should work but the implementation is separated out from the template.

BTW, it is an open source project and I welcome changes like #1.

By: Sproket

Sproket — Fri, 18 Jun 2010 02:53:39 +0000

If you want true logic-less then look at:

http://jolene.sourceforge.net

I don't really bother maintaining it since it works for 99% of my cases. Jolene just reads HTML and stores the DOM as simple JavaScript styled object. It's a true separation of concerns.

By: Koalillo

Koalillo — Fri, 18 Jun 2010 02:46:11 +0000

1. I'd say provide a template lookup interface, handle them just like you do know (i.e. public interface TemplateLookupEngine { public InputStream getTemplate(String name); } or something like that).

2. OK, after re-reading partials I kinda get the idea...

The thing about most template engines I find is that they are either completely tied to the filesystem or that their mechanism for not being tied to the fs is an afterthought. I want my CMS to store templates in the same backend where I store content, with the same properties (i.e. JCR with versioning and branching, etc.).

The other thing is that template inclusion is one of the most important features in a template engine...