doc/guide.html in masterview-0.2.1 vs doc/guide.html in masterview-0.2.2

- old
+ new

@@ -14,16 +14,33 @@ </head> <body> <div id="pageHeader"> -<div>MasterView Template Engine</div> -<div class="description">Rails-optimized (x)html friendly template engine</div> +<a href="index.html"><img id="logo" src="images/masterview_logo.png" alt="MasterView Rails-optimized (x)html friendly template engine"/></a> </div> +<div id="headerNav"> +<div> +&middot;&nbsp; +<a href="./index.html">Doc Home</a> +&nbsp;|&nbsp; +<a href="./installation.html">Installation</a> +&nbsp;|&nbsp; +<a href="./configuration.html">Configuration</a> +&nbsp;|&nbsp; +<a href="./guide.html">Usage</a> +&nbsp;|&nbsp; +<a href="./directives.html">Directives</a> +&nbsp;&nbsp; +<a href="./media_list.html">Media (Videos/Illustrations)</a> +&nbsp;&middot; +</div> +</div> + <div id="pageBody"> -<div id="bodyContent" mv:generate="{template_path}" mv:omit_tag=""> +<div id="bodyContent"> <h1>MasterView - User's Guide</h1> <p> MasterView is designed to be easy @@ -100,9 +117,57 @@ one definition of each part (layout and partial) and they are imported into the other files where needed to provide accurate WYSIWYG design time editing. By generating separate files, teams can work on a project easier, however MasterView also supports generating all parts to a single file for the ultimate in DRY. +</p> +<p> +For example, if our generated Controller name is Store and the Model is Product this is +what would be generated.<br/> +<table id="generatedRhtml"> +<thead> +<tr> +<th>Template</h> +<th>Contained rhtml parts</th> +</tr> +</thead> +<tbody> +<tr> +<td>list.html</td> +<td><b>layout/store.rhtml</b> (layout for the controller)<br/> +<b>store/_messages.rhtml</b> (flash/error messages partial)<br/> +<b>store/_product.rhtml</b> (line partial for each item in list)<br/> +<b>store/list.rhtml</b> (list view) +</td> +</tr> +<tr> +<td>new.html</td> +<td> +<b>store/_form.rhtml</b> (form partial with input fields, used by new and edit)<br/> +<b>store/new.rhtml</b> (new product view) +</td> +</tr> +<tr> +<td>edit.html</td> +<td> +<b>store/edit.rhtml</b> (edit product view) +</td> +</tr> +<tr> +<td>show.html</td> +<td> +<b>store/_show.rhtml</b> (readonly product details partial, used by show and destroy)<br/> +<b>store/show.rhtml</b> (show product view) +</td> +</tr> +<tr> +<td>destroy.html</td> +<td> +<b>store/destroy.rhtml</b> (destroy product view) +</td> +</tr> +</tbody> +</table> </p> <p> By adding the &#8212;single-file switch MasterView will create a single file and to make it easier to use this template at design time, some design time css stylesheets are included in the file to hide all sections except one. \ No newline at end of file