<div>Hi Deb and Jeff,</div>
<div> </div>
<div>thanks for your kind answers!</div>
<div> </div>
<div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>The nicer response is that you need to let go of that attachment to <br>your source formatting. (As did I, in fact).</div></blockquote>
<div> </div>
<div>;-) Well, maybe you are right...</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> It has to be functionally correct <br>and it's nice if it's at least reasonably readable, since in practice
<br>we *do* end up looking at generated page source at various points in <br>web page development (View Source!), </blockquote>
<div> </div>
<div>Not only there, but also the formatting of my static html files generated by masterview</div>
<div>when importing layouts and partials gets changed.</div>
<div> </div>
<div>Anyway, my next "wish" would be to have a possibility to let masterview</div>
<div>generate html files considering the current database content. </div>
<div>This would be very useful, as it comes closer to true wysiwyg editing of </div>
<div>your page and less dummies would be needed. So tables would be filled </div>
<div>with the actual table data instead of dummies. Would that be difficult to </div>
<div>implement? Or is it possible to extend mv with this functionality?</div>
<div> </div>
<div>Another thing that would be very useful for me to have is a way of using</div>
<div>my own layout with mv scaffolding. Ideally I'd like to be able to do </div>
<div>something like the following:</div>
<ul>
<li>Create my layout, including navigation etc.</li>
<li>Define a standard way crud views and partials are generated from models </li>
<li>Using this standard for any further model to quickly setup new model views, like this:</li></ul>
<p>...mv:import="layouts/mylayout.rhtml"...</p>
<p> ...mv:content="@content_for_layout"...</p>
<p> mv:generate_crud=" :model => 'myModel', :layout => 'myLayout.html', :crudLayout => 'myCrudLayout' "</p>
<div>This would then generate the list view of the model in place, separate files for new, edit, </div>
<div>view and delete, using my custom templates and the corresponding actions. That, would be great! </div>
<div>Right now I'm manually typing in the code for all the different models I have, copy and pasting </div>
<div>pieces from the mv scaffolds and adjusting them to my needs, which is quite tedious and not all too dry.</div>
<div>What I have in mind is a kind of a finer grained custom scaffolding. There could be also</div>
<div> defaults/naming conventions for the locations of the custom made layouta and crud styles. </div>
<div>There could be also parameters to select which crud actions and views should be generated and </div>
<div>which shouldn't. Also it would be great if the controller could be specified if not the default is used.</div>
<div>Well, the possibilities seem endless... ;-)</div>
<div> </div>
<div>Does this idea make sense? Is it possible to extend mv like this? I haven't looked much into the </div>
<div>developers section yet.</div>
<div> </div>
<div>Nico</div>
<div> </div>
<div>P.S.: How can I post to a thread instead of making a new one? Do I simply need to use the same subject</div>
<div>text? I try...<br> </div>
<p> </p>
<p> </p>
<div><br> </div> <br> </div>