<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=603173815-15062006>RE: <FONT face="Times New Roman" color=#000000
size=3>mv:generate="{template_dir_path}/{template_basename}.css"
</FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face="Times New Roman" color=#000000 size=3><SPAN
class=603173815-15062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=603173815-15062006>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 face=Arial color=#0000ff size=2><SPAN
class=603173815-15062006></SPAN></FONT><FONT face=Arial color=#0000ff
size=2><SPAN class=603173815-15062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT><SPAN
class=603173815-15062006>{template_path_base}</SPAN></FONT><SPAN
class=603173815-15062006><FONT face=Arial color=#0000ff 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 class=603173815-15062006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=603173815-15062006><FONT face=Arial
color=#0000ff 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 face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=603173815-15062006>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 face=Arial color=#0000ff size=2><SPAN
class=603173815-15062006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=603173815-15062006>~
Deb</SPAN></FONT><BR></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Jeff Barczewski
[mailto:jeff.barczewski@gmail.com] <BR><B>Sent:</B> Thursday, June 15, 2006 8:33
AM<BR><B>To:</B> djlewis@acm.org;
masterview-devel@rubyforge.org<BR><B>Subject:</B> Re: [Masterview-devel]
Integration status<BR></FONT><BR></DIV>
<DIV></DIV>Yes, this is how the keyword expander is currently implemented, it
actually just replaces the token inside of the {}. <BR><BR>Currently to do what
you were trying to do you would use the
following<BR>mv:generate="{template_dir_path}/{template_basename}.css" <BR><BR>I
think it is important to not blur the lines between what is substituted since if
there is business logic that is used in addition the the token itself then this
would be confusing. This also keeps our keyword substitution light and simple
which can be used for other things and not too customized for this one case.
<BR><BR>If you want we can create another different token which represents
{template_dir_path}/{template_basename} to make it simpler for the user to use,
but I think it is important for this to be different than the token we are using
to represent template path with default extension. <BR><BR>So if you want we can
create {template_path_no_ext} or {template_path_base} or something similar which
logically consists of {template_dir_path}/{template_basename} .<BR><BR>What do
you think? </BODY></HTML>