<!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><SPAN class=943212305-06072006></SPAN><FONT
face=Arial><FONT color=#0000ff><FONT size=2>><SPAN
class=943212305-06072006> > </SPAN></FONT></FONT></FONT>Second idea,
MasterView could also be great for maintaining static sites too <SPAN
class=943212305-06072006><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=943212305-06072006><FONT face=Arial
color=#0000ff size=2>>></FONT> </SPAN>since the rebuild recreates all
the pages using any shared layouts and partials. I<SPAN
class=943212305-06072006><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=943212305-06072006><FONT face=Arial
color=#0000ff size=2>>></FONT> </SPAN> hadn't thought about it in
that way, but since the templates are full html copies <SPAN
class=943212305-06072006><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=943212305-06072006><FONT face=Arial
color=#0000ff size=2>>> </FONT> </SPAN>of the pages, they would work
well in a static site. No need to use a rails app <SPAN
class=943212305-06072006><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=943212305-06072006><FONT face=Arial
color=#0000ff size=2>>></FONT> </SPAN>and walk the tree to generate
html. We could do this for our documentation pages, <SPAN
class=943212305-06072006><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=943212305-06072006><FONT face=Arial
color=#0000ff size=2>>> </FONT> </SPAN>although the directives seem
to be saying use a db, everything else is pretty static. <BR><SPAN
class=943212305-06072006><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=943212305-06072006><FONT face=Arial
color=#0000ff size=2>Yes, that's kind of the way I'm using MV right now for
some things, just trying to make it easier to shift some existing static site
content into rails and leverlage a framework that eliminates the
problem of manually duplicating framing layouts and nav
elements across a set of pages. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=943212305-06072006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=943212305-06072006><FONT face=Arial
color=#0000ff size=2>Which is... exactly what we're doing with our own MV
docs. That's been one of my backburner projects, to try using MV on its
own doc pages so we can effectively use layouts and offline generation of the
static set of pages published in doc.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=943212305-06072006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=943212305-06072006><FONT face=Arial
color=#0000ff size=2>This would actually be a good demonstration of MV's
versatility and provide an example of using it outside rails while still
exploiting some of the power of rails and ruby facilities. We should put
this on our todo list!</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=943212305-06072006></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=943212305-06072006><FONT face=Arial
color=#0000ff size=2>~ Deb</FONT> </SPAN><BR><BR></DIV></BODY></HTML>