Comments on: Down with HTML + Code Markup!

By: tim hj

tim hj — Thu, 05 Jun 2008 08:27:23 +0000

Can I ask who or what you were building the $link.’click here’ app for?

It’s a long shot but the server logs for one of our sites has been peppered with
GET /recipes/collections/easy/click%20here HTTP/1.1
GET /recipes/1266/click%20here HTTP/1.1
GET /page/delicious/click%20here HTTP/1.1
etc. requests the past couple of days and we have no idea what’s spawning them. - half of the requests don’t resolve to proper pages…

By: Shams Mahmood

Shams Mahmood — Sat, 17 May 2008 13:19:56 +0000

You must have a look at the wicket framework. It’s one of the reasons I love wicket - separate java code from html.

By: Bob

Bob — Sat, 17 May 2008 06:12:30 +0000

Have a look at Erector: http://erector.rubyforge.org/

By: makoto kuwata

makoto kuwata — Sat, 17 May 2008 03:45:28 +0000

How about Kwartz?
Kwartz separates the presentation logic from the HTML template in the same way CSS separates design from HTML.
As the result, template is pure HTML and it's design is never broken.
In addition, Kwartz can generate eRuby file from HTML template.
I think you should try it if you are looking for the best solution.

By: Jesse

Jesse — Sat, 17 May 2008 02:48:17 +0000

Having to use template language syntax between the brackets drives me nuts as well, especially when I see someone drop a whole if statement in there. I don’t use rails anymore but I am currently in the middle of refactoring ALL our front-end code at work (Freemarker) and went from simply creating a css framework to fix some inconsistencies I was noticing (not to mention trim ~1600 lines of rounded corner rules down to about 80 for the entire site) to building a series of macros/helper functions so there’s no need to write yet another “Top Photos” module for “new page X”. While I did this all mostly to speed up dev time of new features by introducing a framework of common elements/modules, it will also help avoid introducing bad markup since the “new hire” only needs to call a macro.

By: Anonymous

Anonymous — Sat, 17 May 2008 01:37:39 +0000

I tested HAML, Markaby, and Liquid in the book. Markaby is very attractive, but reportedly too slow for a high-traffic system. Liquid is most suited to a case where you need to prevent designers from accessing some functionality. HAML I found kind of opaque and hard to read.

By: Brian

Brian — Fri, 16 May 2008 23:21:15 +0000

Have you looked into using HAML instead of ERb? Your div example would look something like

.thing{:id => dom_id(@thing)}