<!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.2912" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006>Jeff - by all means do the update for mongrel
today. (and include your fine new diagrams!)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006>I'll look at the naming/config issue for assert
refs and get back to you asap, but have meetings this morning so I'll have
to juggle it in. Suggest not holding the update for this; let's
not rush config additions and names until we've had a chance to
consider properly, better to let it wait a day .</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006>Ed's example is actually a case I've already run into
with my own stylesheets and images, so it was already kind of in my mind to
look at while going over directives impls and asset support. I think
his suggestion is on the right track, it's roughly what I'd been
thinking of. I keep a separate design-time stash of stylesheets that have
a more palatable rel ref for use in my MasterView templates; the stylesheets
themselves actually just contain the nasty ../../public/stylesheets sorts of
paths (and can be easily replaced or modified when working separately from my
rails dev setup), along with any design-time overrides/additions I want in my
styles.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006>~ Deb</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006>>> <FONT face="Times New Roman" color=#000000
size=3>I added the feature to image_tag, stylesheet_link, and javascript_include
so that </FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006><FONT face="Times New Roman" color=#000000
size=3>>> if you don't specify an absolute in the attr_value that it will
use a regular expression</FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006><FONT face="Times New Roman" color=#000000
size=3>>> to find the relative path from the src attribute. Currently
these are constants </FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006><FONT face="Times New Roman" color=#000000
size=3>>> embedded in each of these three directives, however after
talking with Ed Howland </FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006><FONT face="Times New Roman" color=#000000
size=3>>> one of our users, the way he was using things it might be better
if these are </FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=124364314-28062006><FONT face="Times New Roman" color=#000000
size=3>>> configurable constants.
</FONT></SPAN></FONT></DIV></BODY></HTML>