Deb Lewis
2006-Jun-04 23:02 UTC
[Masterview-devel] Comment template substitution fields proposal
>> ruby inline substitution is fineok, if you''re happy with that then we''ll go with I already have working Just in case I wasn''t clear, the variable substitution in the generated-file comment template occurs at template processing time; it doesn''t go into the template output file as an erb field in the generated rhtml. So the reference #{template_path} or <%= template_path %> (or {{{template_path}}}...), depending on our notation choice, is only used when an app developer sets the MasterView configuration setting for the comment content and is resolved during template processing - the output rhmtl that''s generated looks exactly like it does now. The only real differentiator is what''s the likely mind-set when you sit down to write a config/masterview/settings.rb file. When you install a customized value for the generated-file comment, are you thinking "I''m writing a ruby string literal that will have double-quote substitution processing" or is it easier to think "I''m writing a string that''s an ERB template" A MasterView programmer probably has both of those mind-sets, so to me it''s really a tossup. ~ Deb -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20060604/71bbe96b/attachment.htm