Jaderl - 18 months on . . .

[Graeme Defty]

Jesse,

As I stated in my original message describing it, the initial version of Jade which I wrote was missing the multi-file features (-include, -mixin, etc) which rendered it pretty much unusable. I did call it a Jade "toy" in my original posting (https://groups.google.com/forum/#!topic/chicagoboss/hLvhKJUDfLg) Somhow though, it became a "feature" of CB and therefore in its current state must be a disappointment to anyone trying it.

I assume that the fact that nobody is howling means that nobody is using it, because for me at least the missing features are must-have items.

Anyway, I have finally got back to working on it. I have 'include's working and expect to have 'extend's and 'mixin's ready pretty soon.

I have taken a fork on github and will generate a pull request if you let me know to whom, what branch or whatever I should do it.

There should be a couple more to come with the remaining couple of missing features.

I really would like to get this finished. ErlyDTL is no worse than other templating languages, but it is no better either. To my mind, Jade (and Slim and the like) lift templating to a usable level so I am keen to get this production-ready.

Thanks,

graeme

[Adam Veldhousen]

This is probably the best news I've heard all week. Extend/include/mixin support will probably be enough for this to get widespread use (Jade is more approachable to a newbie also, imo). The one issue that I've noticed is that the docs don't tend to get updated, and the tutorials seem to push people into ErlyDTL to the point that they may not even be aware of Jade templating support. Hopefully that changes.

[Andreas Stenius]

Hi Graeme,

I have plans to make erlydtl into several template components, so you can mix and match the syntax, ast and compiler to fit your needs.

This way, it should be feasible to have a jade syntax parsed into a ast tree that you can compile with the erlydtl compiler. I'm not familiar with jade, nor how mixins work in that language, so there may be some things missing. But includes and a whole bunch of other stuff you'd get for free.

Not sure if this would interest you at all.. but if you'd like to join in on that, we could get a pretty nice template compiler engine.

Cheers
Andreas (@kaos on gh)

--
You received this message because you are subscribed to the Google Groups "ChicagoBoss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chicagoboss...@googlegroups.com.
Visit this group at http://groups.google.com/group/chicagoboss.
To view this discussion on the web visit https://groups.google.com/d/msgid/chicagoboss/CAKF5fiBTqKVpbLmp9VwyK99reW7Z%3Dga4Z%2BY9xnpj45q%2Bbop2zQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Graeme Defty]

Hi Andreas,

When I wrote Jaderl I did have in mind the idea of separating compilation (into an AST) from generation (from AST to HTML), and hence Jaderl is structured in exactly that way. I anticipated multiple parsers for different templating languages, and (hopefully only) one generator.

I have not looked yet at the source of ErlyDTL, so I am not sure if it already employs such a structure, but if not then the nodes I defined for the AST (I think I called it HST - HTML Syntax Tree) may be of interest to you as a start point.

I am definitely very interested in combining these efforts, and have always seen the careful and clear spec of the AST to be a key factor in achieving this goal.

graeme

PS

I am guessing that this topic is likely to be of only peripheral interest to most readers of this list. Do you plan an alternative venue for the anticipated discussions?

To view this discussion on the web visit https://groups.google.com/d/msgid/chicagoboss/CABCxKreqPr0VidukhMAFy9MRE0z7h_rb4Fw6Qeg68UfjZSUgXw%40mail.gmail.com.

[Andreas Stenius]

Hi Graeme,

I think we could move this thread to the erlydtl users list (and/or as comments on a github issue). I keep the cb list a final time, to not leave a trail to follow..

I'm glad you've also been thinking along the same lines regarding the template compiler.

During the spring, I refactored the erlydtl code in order to make the different stages more decoupled (erlydtl does indeed have these stages already). It's not all done yet, however.

ErlyDTL Issue 143 relates to this discussion as well: https://github.com/erlydtl/erlydtl/issues/143

I think that would be a good first step, to get a common AST format spec'ed out.

Cheers

To view this discussion on the web visit https://groups.google.com/d/msgid/chicagoboss/CAKF5fiB_N_pb85e-Ew4kPPy4c9zX-dDr%2BBYJ87E%3DJZM9bj8a_A%40mail.gmail.com.