Sounds good. <br><br>I am fine with changing keyword expansion to either have another expansion word, or if you want to simply make {template_path} the one without extension then I that would work as well. <br><br>We could put the logic into the generate tag to always add default extension if one doesn't exist. In essence this would give you what you were hoping for.
<br><br>mv:generate="{template_path}" generates foo/bar.defaultExtension<br>mv:generate="{template_path}.css" generates foo/bar.css<br><br>I guess maybe I should have thought about doing it that way rather then changing the keyword expander. It does seem reasonable to me to do things this way if we do it in the generator logic. I don't know how much code this will affect, but most likely parser code that handles generator directive, and some work in the analyzer since I have to do keyword expansion and some substitution to be able to compare sections to determine if an imported section is out of date with another. Basically if they specified literally
foo.bar in one place and in another file they imported {template_path} that expands to foo.bar in another. Logically those are the same so my comparison needs to indicate that. Rebuild or copy currently forces the built files to have their keywords expanded since it is too difficult to accomplish otherwise.
<br><br>Let me know what you think and whether this is something that you want in there real soon or if it could wait a while. I would like to firm up the keywords themselves before next release, but if you felt that the adding default extension in generator is low priority then we could wait with that until later and not mess up anything we have defined.
<br><br><div><span class="gmail_quote">On 6/15/06, <b class="gmail_sendername">Deb Lewis</b> <<a href="mailto:djlewis@acm.org">djlewis@acm.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span>RE: <font color="#000000" face="Times New Roman" size="3">mv:generate="{template_dir_path}/{template_basename}.css"
</font></span></font></div>
<div dir="ltr" align="left"><font color="#000000" face="Times New Roman" size="3"><span></span></font> </div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span>way too verbose, even for me, but your argument about
clearly distinguishing when default extension will be used vs. not is
good.</span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span></span></font><font color="#0000ff" face="Arial" size="2"><span></span></font> </div>
<div dir="ltr" align="left"><font><span>{template_path_base}</span></font><span><font color="#0000ff" face="Arial" size="2"> might work,
but alternatively maybe we need to revisit {template_path}, it's a bit confusing
relative to the other keyword. Lemme think on this a bit more this
morning.</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">[fwiw, I think I'm going to stop using my generates that
are dumping out local <style> decls, but I'm keeping for the moment
because it turns out to be a good test case for playing with our new target
notations]</font></span></div>
<div><font color="#0000ff" face="Arial" size="2"></font> </div>
<div><font color="#0000ff" face="Arial" size="2"><span>btw
your new version of test/unit/template_spec_test fixed my unit test failure, but
am tinkering a bit more with paths and roots and init this morning. Want
to test a bit more on my own rails app and in clean installs before commiting,
but I think I can submit today.</span></font></div>
<div><font color="#0000ff" face="Arial" size="2"><span></span></font> </div>
<div><font color="#0000ff" face="Arial" size="2"><span>~
Deb</span></font></div></div></div></blockquote></div><br>