> But in your example, if I change my variable name, I have to change 
> the template, as with cgikit, I just have to change the binding, which 
> is a much smaller and
> simpler file than the template.

well, but if you replace the 'address' variable with 'address1' and 
'address2'
in your ruby code, you will have to change the binding AND the template.


> Anyway, we've come to a point where we discuss really minor things. 
> I'll test
> Rails to get a better idea of how I can limit my code in the template, 
> and
> I encourage you to test cgikit, if only to confirm your opinion on the 
> <cgikit> tags ;-)

great! i think trying things out, especially with real life projects is 
always
the best thing..

i never tried cgikit i have to admit, but i used something somewhat 
similar for a couple
of projects:
http://wact.sourceforge.net/

basically i had the same concerns there and really started to curse 
every time i was
forced to do something programming like in xml.. (yes, i even had worse 
programming
in xml experiences. i did quite a bit of work in xslt =)

i admit that neither of the two options (ruby in the template or pure 
xml-template) is
the perfect solution for every project. it all depends on whats 
important for you and
what your requirements are.