realistschuckle/gohaml — Issue #3: Features not up to par with "templates"
Author: bmatsuo
Created: 2011-11-21 14:55:50+00:00
State: open

I like this project. The haml-to-html translation seems pretty solid. And, I really want to use haml to write web-apps with Go and Google App Engine.

But, the template capabilities of gohaml are not good enough, imho. If you look at [the "template" godoc page](http://golang.org/pkg/template), there are obviously a number of features provided by it which are not by gohaml.

Bringing gohaml up to par with "template" is going to take a lot of work. And I don't want to just dump it all on you, demanding an amazing haml template library.

However, it sounds like more work than I *really* want to do. So, I forked this project because I have a plan and I want to hear your thoughts.

The Go authors have done a lot of good work with their template package. And you've done a lot of good work here with you're haml parser. I'm going to chain them together.

I'm making the haml parser output a template which i'll feed into a template parser. I'm sure it will work. And, I think the output as well as the new code will be pretty clean. I'm concerned about the time it would take to parse twice, because they can't be done concurrently.

If you don't want any part of this, I might break my fork off into a new repository, and I'd encourage you to keep working on adding things like embedding other templates using a [Set](http://golang.org/pkg/template/#Set) type structure. Things like function/method calls would be really nice to.

Thanks for all the hard work you put in writing this great parser. =)

Cheers,

Bryan