Displaying 2 results from an estimated 2 matches for "template_exists".
2006 Mar 12
0
ERB and Builder template engines shouldn''t be so heavily wired in ActionView::Base
...The ActionView::Base should work just like a register / dispatcher for
template engines.
2. Every template engine (including ERB and Builder) should be placed
inside the vendor directory.
3. Every template engine should have a base class
ActionView::Engines::EngineName with these methods:
self::template_exists?( render_options={} )
self::type # return :rhtml, :rxml, :vcrb, etc.
initialize( action_view )
render( render_options={}, local_assigns={} )
4. Only used template engines will be then registered in environment.rb:
ActionView::Base.register_template_handler( ''erb'' )
# does: requ...
2007 Jan 25
2
render .rhtmlx if present, otherwise render .rhtml
We have a product where our customer is "allowed" to make minor changes
to the .rhtml views.
Obviously, this can be an issue when updating the software, as changes
need to be merged in. Also, sometimes the customer wants to back out
there change but no longer has the original file.
SOOO....
I''d like to tell them
- if you want to change a .rhtml file
- just copy it to