Masterview devel - Nov 2006 - At last, MasterView article!!!!!!

On 11/8/06, Hendy Irawan <gauldong at gmail.com>
wrote:
>
> Arghh.... After several weeks now I can make it live.
>
>
>
http://web2withrubyonrails.gauldong.net/2006/11/08/easily-maintainable-designer-friendly-actionview-templates-using-masterview-liquid/
>
> It''d be great if you''d visit it and tell me what you
think.
>
> It has barely touched anything, but demonstrates a good (I think)
> sample and in concert with Liquid. I think they make perfect mates.
> And I intentionally put multiple yield''s in the same template, and
> also one sample uses mv:generate while the other uses render_partial
> inside content_for that uses actual Liquid template. I think it''s
one
> alternative (weird?) way to set up Rails but I guess it can be done
> and may actually be useful.
>
> Thanks for the images explanation, I thought I''ve read about that
> before somewhere but forgot it... It surely makes MasterView very very
> useful.
>
> Note that Nvu still doesn''t work and this is Nvu''s fault.
I don''t see
> a way turning off their ''tidy''ing feature. Lots of
WYSIWYG editors now
> automatically ''tidy'' without mercy, I hate them.


Nice article Hendy!! You did a good job of cutting to the meat of the
topics.  I love the visuals you put together, that really helps. I think
some of what you have done will help inspire us further with our
documentation.

I might suggest one minor clarification, the masterview admin page is
configurable as to whether it is enabled. By default it is only enabled in
development mode (not production) and also currently it is only available
from localhost not remote locations. We plan on enhancing the authentication
around this but took these steps to keep things relatively safe now. If you
want I can post this in comments to your site to help clarify.

NVU definitely needs a bit of work. There is a setting that is supposed to
leave your code as is, but it only partially works. And it also seems to
generate bad xhtml (no matter what you set the settings to). So one of these
days I hope to jump in there and fix both of those problems because
otherwise I think it has some good potential. I just need more time to do
everything I would like :-)

I am planning on putting on the todo list, the ability to make safe
templates with MasterView too since I agree there is a need for that where
consumers are going to change things. So I think we can clean that up even
further.

Thanks for mentioning the project in your article. We have some great things
coming in the next year, so stay tuned. And if you get some additional great
ideas, keep them coming.

All the best,

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