Masterview devel - Jun 2006 - Comment template substitution fields proposal

RE: long-term goal to eliminate the generated .rhtml erb files
 
oh, lovely indeed.  That''s exactly what I started out looking at doing
on my
own a few weeks ago, before deciding it wasn''t a quick hack - I wanted
to
write my app/views as .pt files (as in zope page templates) which just
magically did the right thing through the same caching cleverness that
that''s used for .rhtml templates in there now.
 
Wasn''t sure if you were ready to hear a proposal for that notion, since
clearly there''s plenty of other things to do just with the current
scheme.
So - thank you for sharing that thought!
 
Definitely put this in a "future directions" section in the docs.
 
~ Deb

  _____  

From: Jeff Barczewski [mailto:jeff.barczewski at gmail.com] 
Sent: Saturday, June 03, 2006 3:19 PM
To: djlewis at acm.org
Subject: Re: [Masterview-devel] Comment template substitution fields
proposal


That sounds fine to me. ruby inline substitution is fine. If you need me to
help with any of this let me know. 

Also just to keep you up to date with my current thoughts, the long term
plan is to eliminate the need for erb generation at all. I started out this
way so that it would be easy to develop and easy to debug. n the future erb
generation will be configurable since it won''t technically be needed if
we
load the compiled erb directly into the rails erb cache. 

This will eliminate clutter and confusion from having these generated rhtml
files. Of course we could allow it to be configured to generate them anyway.
I also envisioned a way to request the erb file off of the masterview admin
pages or via rake tasks if for any reason one wants to get the files. 

But there are many things to figure out and test before we go down that
path.

Jeff

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060603/8a025b07/attachment.htm