From: Martin DeMello <martindemello@...>
Date: 2004-07-30T17:51:44+09:00
Subject: Re: rubyonrails and cgikit comparison

Kirk Haines <khaines@enigo.com> wrote:
> Every time page content changes, the CMS system will regenerate the 
> component into a static file.  I actually did this because it now lets me 
> provide dynamic capabilities to clients in the form of Iowa components that 
> they can just include into their web pages via the CMS system.  So, one 
> company might have access to a set of components that allows data entry and 
> report generation, and they can control where and how those capabilities are 
> reached simply by embedding something like:
> 
> <IssueView idx="7"/>

This bit sounds interesting - I've mentally bookmarked it for if I ever
do something on that scale. I'm afraid that for small scale work all I'd
really be using it for is Yet Another Template System.

For a concrete example of the type of thing I'm talking about, the first
time around I did http://zem.novylen.net/filk/filkindex.html using a
handrolled template, manually running a ruby script to generate the HTML
files from some minimally marked-up text and scping them over to my
public_html directory. I've been meaning to rewrite that using a cron
job that scans a 'source' directory for incoming files and generates the
html pages itself. I was going to do it using a template as usual, but
the post that kicked off this subhread reminded me of my abortive
efforts to do it all with CGI.rb's html generation made me wonder if
someone had come up with a better way.

martin