<!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=897100705-06072006>Jeff - thanks for the explanations of some of your
thinking. Let'd not do anything right now about this - my config
change to restrict MV template processing to specific subdir of my
app/views can be considered a side effect of earlier versions when we were
generating .rhtml files back into views. I don't think it's that
interesting now that we compile directly into the view cache, so unless there's
issue such as perf that would lead you to want to restrict the template checking
I'd say leave it be.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=897100705-06072006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=897100705-06072006>I changed my config back to leave the default app/views
as the template src/dst dir settings and I'm once again a happy masterview
user.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=897100705-06072006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=897100705-06072006>This would be a good for the "tips and troubleshooting"
doc that we need to write one of these days, though - someone might run into
this and it's quite baffling, took me several hours to hunt down the
problem.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=897100705-06072006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=897100705-06072006>Side note: we'd briefly kicked around some
thoughts on whether it might be important to be able to specify some of the
config settings on multiple MIO trees vs. the single MIO structure that we
currently have. Was thinking about that and I'm informally convinced that
it would be fairly do-able without breaking the existing config protocol if we
ever wanted to do so. To support multiple MIO trees, existing protocol
would remain and map behind the scenes to the "primary" MIO tree, with some
additional protocol provided to allow adding and configuring options for
additional sections.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=897100705-06072006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=897100705-06072006>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=897100705-06072006>~
Deb</SPAN></FONT></DIV></SPAN></FONT></DIV></BODY></HTML>