Comments for fmap fix return

Comment on HStringTemplate: An Elegant, Functional, Nifty Templating Engine for Haskell. by gwern

gwern — Fri, 12 Nov 2010 19:50:53 +0000

http://code.haskell.org/HStringTemplate/dist/doc/html/hstringtemplate/Text-StringTemplate.html is broken link. Perhaps link to something like http://hackage.haskell.org/packages/archive/HStringTemplate/0.6.5/doc/html/Text-StringTemplate.html ?

Comment on ANN: hvac 0.1b, a transactional, declarative framework for lightweight web applications by Demystifying hvac – Making sense of all the symbols. « archive from dbpatterson.com

Tue, 08 Sep 2009 19:22:27 +0000

[…] is a new, extremely lightweight web framework written in haskell. To learn more about it, check out the hvac announcement . The purpose of this short article is to try to make sense of all the symbols that you will […]

Comment on ANN: hvac 0.1b, a transactional, declarative framework for lightweight web applications by Zoneaire

Zoneaire — Thu, 02 Apr 2009 17:35:58 +0000

Very interesting program, and intelligently made.

Comment on Some concepts behind hvac by Art Silver

Art Silver — Wed, 18 Mar 2009 00:39:05 +0000

I’m looking forward to more about templates.

Comment on ANN: hvac 0.1b, a transactional, declarative framework for lightweight web applications by Art Silver

Art Silver — Wed, 18 Mar 2009 00:36:11 +0000

Nice framework idea. Most tend to be bloated and try to be the end all be all of coding.

Comment on Comonads in everyday life. by Artyom Shalkhakov

Artyom Shalkhakov — Mon, 26 Jan 2009 10:05:36 +0000

Thanks for the great post.

After a week of lurking I finally understand how to use this stuff.

The function “menuRows” turned out to be the most difficult to understand, BTW. :)

Comment on Some concepts behind hvac by Jochem Berndsen

Jochem Berndsen — Fri, 26 Dec 2008 00:37:01 +0000

After some fiddling with hvac + lighttpd, I came to the conclusion that the lighttpd-packages in Debian testing are *broken*. (Maybe also in Ubuntu). The latest version on 1.4.20 works, however. My config, for the example, is as follows:

server.document-root = “/var/www”
server.modules = ( “mod_fastcgi” )
server.port = 3000

fastcgi.debug = 1
fastcgi.server = ( “/test” =>
(
(
“socket” => “/tmp/test.sock”,
“bin-path” => “/path/to/hvac-board”,
“min-procs” => 1,
“max-procs” => 1,
“check-local” => “disable”
)
)
)

Comment on HStringTemplate: An Elegant, Functional, Nifty Templating Engine for Haskell. by New Adventures in Software » Generating HTML with Haskell

New Adventures in Software » Generating HTML with Haskell — Wed, 03 Dec 2008 19:49:00 +0000

[…] HStringTemplate is a Haskell port of Terence Parr’s StringTemplate engine (originally for Java but also available for C# and Python). StringTemplate is a templating engine along the lines of Apache Velocity but is more restrictive in what processing it permits templates to perform. Specifically, it strictly enforces separation between model and view. It is not possible for a template to cause side-effects elsewhere (no database updates, etc.). StringTemplate can be used for generating any kind of text output, not just XML/HTML. In fact, one of its principal uses is as a code generator for ANTLR. […]

Comment on HStringTemplate: An Elegant, Functional, Nifty Templating Engine for Haskell. by Artyom Shalkhakov

Artyom Shalkhakov — Wed, 22 Oct 2008 09:32:31 +0000

It looks like this templating system completely lacks computation of any kind (you can’t add two numbers within template, can you?).

I find this somewhat confusing. Do you know of XSLT? It looks pretty much the same (no side-effects, support for recursive template substitution, etc.), except for many-many details (syntax, functions, etc.). :)

Do you think it is better to compute everything outside of templates? And how about treating output as a document (not a raw string)? I suppose it would reduce the number of common syntactical errors, as well as provide some output validation.

Comment on HStringTemplate: An Elegant, Functional, Nifty Templating Engine for Haskell. by Dietrich Epp

Dietrich Epp — Sun, 03 Aug 2008 23:25:13 +0000

In response to George, it took a little time for me to get used to the most elegant way to order function arguments. Take a look at the types in Data.Map, for example, insert is k -> a -> Map k a -> Map k a. This order supports currying of the template, so I can do:

setMyAttributes = setAttribute “key1” “value1” . setAttribute “key2” “value2”

Instead of:

setMyAttributes t = setAttribute (setAttribute “key2” “value2” t) “key1” “value1”