Masterview devel - Jul 2006 - Couple ideas for MasterView - interactive parsing page, using MV for static sites as well

Just a couple ideas I had that I thought I would share

One thing that will make it easier to experiment and understand MasterView
is if I provide an interactive parsing page from the admin pages.

This could basically be a screen with a text area that you can put in
template html and click parse and it will show you the resultant rhtml
outputs. It would be designed that you could easily change something and
then resubmit allowing you to iteratively try things and learn. Another
simple thing we can do is to allow that page to have access to a bunch of
samples as well, so clicking on a link for the text_field directive might
give you a nice example for that all ready to run and edit. So this way we
can have an interactive help so people can learn and get comfortable with
the syntax. Just a simple controller and view is all that is needed to make
this work, we have all the rest of the plumbing.

Second idea, MasterView could also be great for maintaining static sites too
since the rebuild recreates all the pages using any shared layouts and
partials. I hadn''t thought about it in that way, but since the
templates are
full html copies of the pages, they would work well in a static site. No
need to use a rails app and walk the tree to generate html. We could do this
for our documentation pages, although the directives seem to be saying use a
db, everything else is pretty static.

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060705/392fc536/attachment.html

> > Second idea, MasterView could also be great for maintaining static
sites
too  
>> since the rebuild recreates all the pages using any shared layouts and
partials. I 
>>  hadn''t thought about it in that way, but since the templates
are full
html copies  
>>  of the pages, they would work well in a static site. No need to use a
rails app  
>> and walk the tree to generate html. We could do this for our
documentation pages,  
>>  although the directives seem to be saying use a db, everything else is
pretty static. 
 
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.  
 
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.
 
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!
 
~ Deb 


-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060706/5289c1c7/attachment.html