Comments on: Introducing ErlTL: A Simple Erlang Template Language

By: Daniel Kwiecinski

Daniel Kwiecinski — Fri, 16 Mar 2007 16:25:41 +0000

If the *.et files contains top level expresions not in the first line (as in album.et) and are saved with Windows style line ending (CR+LF) instead of Unix one (LF), during the compilation I got the following error:

{error,{misplaced_top_exprs,{{line,2},
{chunk,” {Title, Artist, Songs} = Data %>\r”},
{msg,”top expressions must appear before all other expressions in a function”}}}}

Cheers,
Daniel

By: Dru Nelson

Dru Nelson — Fri, 12 Jan 2007 08:31:29 +0000

just saw this on Reddit, I think this is a great tool for Erlang!

By: taide

taide — Mon, 23 Oct 2006 18:23:45 +0000

Check this for inspiration, it’s very good: http://www.kieranholland.com/code/documentation/nevow-stan/

By: taide

taide — Mon, 23 Oct 2006 18:23:36 +0000

Check this for inspiration, it’s very good: http://www.kieranholland.com/code/documentation/nevow-stan/

By: Yariv

Yariv — Wed, 18 Oct 2006 13:07:12 +0000

Hi Dmitirii, I think ErlTL will work at least with UTF8 encoding, but I haven’t tried it myself. Would you like to give it a test drive and tell me what happens. If there are problems, I may be able to find a solution to dealing with different encoding schemes.

By: Dmitrii Dimandt aka Mamut

Dmitrii Dimandt aka Mamut — Wed, 18 Oct 2006 01:31:05 +0000

What about non-ASCII :)

Will ErlT be able to compile templates with, say, Unicode data in them?

The usual amount of drooling goes here :))

By: Yariv

Yariv — Tue, 17 Oct 2006 17:42:19 +0000

(Another advantage to ErlTL is that with ErlTL, Yaws doesn’t have to spend time expanding the ehtml structure.)

By: Yariv

Yariv — Tue, 17 Oct 2006 17:36:52 +0000

I think the two approaches are complementary. When your content is largely programatically generated, it’s easier to work with functions. When you have a lot of static binary text and you want to embed some dynamic expressions inside it, it may be more readable to use a ErlTL template. I think in this example, a hybrid approach could work well:

<code>&amp;lt;html&amp;gt;<br />

&amp;lt;title&amp;gt;&#46;..&amp;lt;/title&amp;gt;<br />

&amp;lt;body&amp;gt;&#46;..&amp;lt;% table(Data) %&amp;gt;&amp;lt;/body&amp;gt;<br />

&amp;lt;/html&amp;gt;</code>

In the end, it’s about readability. In addition, ErlTL helps newbies use binaries by default in places where they may mistakenly use strings.

By: Anon.Coward

Anon.Coward — Tue, 17 Oct 2006 17:30:06 +0000

Nice, but why not simple do it like this:

table([[1,”Come together”],[2,”Something”],…etc…]).

and the definition of table/1;

table(Rows) ->

    {table, [],   td_rows(Rows)}.

 

table(Header, Rows) ->

    table(Header, Rows, []).

 

table([], Rows, Attrs) ->

    {table, lkup(table, Attrs, []),

     [td_rows(Rows)]};

table(Header, Rows, Attrs) ->

    {table, lkup(table, Attrs, []),

     [{tr, [], map(fun(C) -> {th, [], [C]} end, Header)},

      td_rows(Rows)]}.

 

td_rows(Rows) ->

     lists:map(fun(R) ->

                       {tr, [],

                        map(fun(C) -> {td, [], [C]} end, R)}

               end, Rows).

Note: you even get in headers and attributes in the above…

Cheers!