On 10/28/06, Hendy Irawan <gauldong at gmail.com>
wrote:>
> Hi, I''ve tried MasterView. Works great. Some issues (more on these
> later, one of them is that I can''t figure out how to put
<!DOCTYPE on
> top of my output htmls)).
Hmmm, maybe its a bug, I will look into it. Might be an oversite on my part.
> Liquid works fine (very nice). Haven''t tried with Rails Engine and
> theme_support plugin, but expects failure.
>
> Seems that MasterView is quite a "radical" change in development
style
> than plain eRb+rails... What I worry so much is not MasterView itself,
> but whether it works fine with other [plugins|Rails Engines] that
I''m
> going to use/develop...
It is a bit of a conceptual shift, but we try to use rails like syntax
where possible to soften the learning curve. The combined/rolled up
view templates is one of the brand new things to get used to.
As far as working with other things that you will use/develop, one
goal of mine is that MasterView will play nice with other plugins,
templates, etc. So I am trying my best to work within the Rails
framework properly as to be compatible. Currently with rails
generating rhtml it should be very compatible with everything else as
far as coexisting. One can even turn all the magic off and just have
MasterView generate rhtml to the file system and one can even deploy
that rhtml on a production server without MasterView installed, once
the erb is generated it doesn''t rely on anything.
However the magic makes it more fun to work with especially for
development (autogenerating of rhtml on template change...), so I am
trying to make that work seamlessly in the rails framework. The other
question that occurs to me in your question is to use liquid or other
template technology right inside MasterView templates. I haven''t done
anything with that yet, so I will have to look into that to see.
So I guess my thought is that at the moment, I am not aware of any
things that MasterView is not compatible with, if they are used side
by side (MasterView can generate rhtml, including layouts and partials
and you can use those layouts and partials along with any other rails
technology/templates, but I just haven''t tried mixing things in the
templates themselves yet).
I will take a TODO item to look at the doctype issue and to see if and
how we could mix things as well. One obvious step would be to have
directives that generate liquid that way you could have WYSIWYG
editing of the full page. I''ll have to look at all that to see what
would work best. For now though you should be safe in using things
separately (not in the same template).
>
> Conclusions is congratulations for making such a very good product. I
> was also surprised that you had the time to write all that docs &
> guides. You''re a very diligent person. :-) Can''t believe
what your
> work must have been had someone gave you $1 million funding ;-)
Thank you for your time to write and kind words. Actually, I have to
give most of the credit for the document to my wonderful partner, Deb
Lewis, she has worked tirelessly on the documentation and has been
invaluable in helping to extend and refactor MasterView into what it
is now. It would not be half of what it is without all of her help. (I
am copying her on the response so she''ll get to see your comments).
So if you run into any issues with compatibility let us know, I expect
side by side use to work fine. I will keep you posted as we do any
more advanced integration (like liquid directives) between
technologies.
Many blessings to you and your family,
Jeff