http://www.jzlabs.com/2010/03/24/haml-autocompiler/ the web experiment playground of jason ting Mon, 19 Dec 2011 08:12:12 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://www.jzlabs.com/2010/03/24/haml-autocompiler/comment-page-1/#comment-474 Jason Thu, 25 Mar 2010 17:18:25 +0000 http://www.jzlabs.com/?p=344#comment-474 thanks nathan, i will try out those suggestions! thanks nathan, i will try out those suggestions!

]]> http://www.jzlabs.com/2010/03/24/haml-autocompiler/comment-page-1/#comment-473 Nathan Weizenbaum Thu, 25 Mar 2010 11:06:53 +0000 http://www.jzlabs.com/?p=344#comment-473 I have a few suggestions. First, this would probably be significantly faster if it used the Haml Ruby API (see http://haml-lang.com/docs/yardoc/Haml.html). Second, when using the command-line interface, it's preferable to use "haml input.haml output.html", rather than manually redirecting the output in the shell (this way, Haml knows what file it's outputting to and can sometimes provide better debugging information). Third, I would suggest using FSSM (http://github.com/ttilley/fssm) for monitoring the filesystem, which can hook into native filesystem-watchers. I have a few suggestions. First, this would probably be significantly faster if it used the Haml Ruby API (see http://haml-lang.com/docs/yardoc/Haml.html). Second, when using the command-line interface, it’s preferable to use “haml input.haml output.html”, rather than manually redirecting the output in the shell (this way, Haml knows what file it’s outputting to and can sometimes provide better debugging information). Third, I would suggest using FSSM (http://github.com/ttilley/fssm) for monitoring the filesystem, which can hook into native filesystem-watchers.

]]>