Class: Reactive::Mvc::View::Base

Inherits:
Object
  • Object
show all
Extended by:
ActiveSupport::Memoizable
Includes:
CompiledTemplates
Defined in:
lib/reactive-mvc/view/base.rb

Overview

Action View templates can be written in three ways. If the template file has a .erb (or .rhtml) extension then it uses a mixture of ERb (included in Ruby) and HTML. If the template file has a .builder (or .rxml) extension then Jim Weirich’s Builder::XmlMarkup library is used. If the template file has a .rjs extension then it will use ActionView::Helpers::PrototypeHelper::JavaScriptGenerator.

ERb

You trigger ERb by using embeddings such as <% %>, <% -%>, and <%= %>. The <%= %> tag set is used when you want output. Consider the following loop for names:

<b>Names of all the people</b>
<% for person in @people %>
  Name: <%= person.name %><br/>
<% end %>

The loop is setup in regular embedding tags <% %> and the name is written using the output embedding tag <%= %>. Note that this is not just a usage suggestion. Regular output functions like print or puts won’t work with ERb templates. So this would be wrong:

Hi, Mr. <% puts "Frodo" %>

If you absolutely must write from within a function, you can use the TextHelper#concat.

<%- and -%> suppress leading and trailing whitespace, including the trailing newline, and can be used interchangeably with <% and %>.

Using sub templates

Using sub templates allows you to sidestep tedious replication and extract common display structures in shared templates. The classic example is the use of a header and footer (even though the Action Pack-way would be to use Layouts):

<%= render "shared/header" %>
Something really specific and terrific
<%= render "shared/footer" %>

As you see, we use the output embeddings for the render methods. The render call itself will just return a string holding the result of the rendering. The output embedding writes it to the current template.

But you don’t have to restrict yourself to static includes. Templates can share variables amongst themselves by using instance variables defined using the regular embedding tags. Like this:

<% @page_title = "A Wonderful Hello" %>
<%= render "shared/header" %>

Now the header can pick up on the @page_title variable and use it for outputting a title tag:

<title><%= @page_title %></title>

Passing local variables to sub templates

You can pass local variables to sub templates by using a hash with the variable names as keys and the objects as values:

<%= render "shared/header", { :headline => "Welcome", :person => person } %>

These can now be accessed in shared/header with:

Headline: <%= headline %>
First name: <%= person.first_name %>

If you need to find out whether a certain local variable has been assigned a value in a particular render call, you need to use the following pattern:

<% if local_assigns.has_key? :headline %>
  Headline: <%= headline %>
<% end %>

Testing using defined? headline will not work. This is an implementation restriction.

Template caching

By default, Rails will compile each template to a method in order to render it. When you alter a template, Rails will check the file’s modification time and recompile it.

Builder

Builder templates are a more programmatic alternative to ERb. They are especially useful for generating XML content. An XmlMarkup object named xml is automatically made available to templates with a .builder extension.

Here are some basic examples:

xml.em("emphasized")                              # => <em>emphasized</em>
xml.em { xml.b("emph & bold") }                   # => <em><b>emph &amp; bold</b></em>
xml.a("A Link", "href"=>"http://onestepback.org") # => <a href="http://onestepback.org">A Link</a>
xml.target("name"=>"compile", "option"=>"fast")   # => <target option="fast" name="compile"\>
                                                  # NOTE: order of attributes is not specified.

Any method with a block will be treated as an XML markup tag with nested markup in the block. For example, the following:

xml.div {
  xml.h1(@person.name)
  xml.p(@person.bio)
}

would produce something like:

<div>
  <h1>David Heinemeier Hansson</h1>
  <p>A product of Danish Design during the Winter of '79...</p>
</div>

A full-length RSS example actually used on Basecamp:

xml.rss("version" => "2.0", "xmlns:dc" => "http://purl.org/dc/elements/1.1/") do
  xml.channel do
    xml.title(@feed_title)
    xml.link(@url)
    xml.description "Basecamp: Recent items"
    xml.language "en-us"
    xml.ttl "40"

    for item in @recent_items
      xml.item do
        xml.title(item_title(item))
        xml.description(item_description(item)) if item_description(item)
        xml.pubDate(item_pubDate(item))
        xml.guid(@person.firm..url + @recent_items.url(item))
        xml.link(@person.firm..url + @recent_items.url(item))

        xml.tag!("dc:creator", item.author_name) if item_has_creator?(item)
      end
    end
  end
end

More builder documentation can be found at builder.rubyforge.org.

JavaScriptGenerator

JavaScriptGenerator templates end in .rjs. Unlike conventional templates which are used to render the results of an action, these templates generate instructions on how to modify an already rendered page. This makes it easy to modify multiple elements on your page in one declarative Ajax response. Actions with these templates are called in the background with Ajax and make updates to the page where the request originated from.

An instance of the JavaScriptGenerator object named page is automatically made available to your template, which is implicitly wrapped in an ActionView::Helpers::PrototypeHelper#update_page block.

When an .rjs action is called with link_to_remote, the generated JavaScript is automatically evaluated. Example:

link_to_remote :url => {:action => 'delete'}

The subsequently rendered delete.rjs might look like:

page.replace_html  'sidebar', :partial => 'sidebar'
page.remove        "person-#{@person.id}"
page.visual_effect :highlight, 'user-list'

This refreshes the sidebar, removes a person element and highlights the user list.

See the ActionView::Helpers::PrototypeHelper::GeneratorMethods documentation for more details.

Defined Under Namespace

Modules: CompiledTemplates Classes: ProxyModule

Constant Summary collapse

@@format_handlers =

TODO: format_handlers should be local to each descendant! not shared amongs all the hierarchy (because same format may be handled by different handlers in children classes)

{}
@@exempt_from_layout =

Templates that are exempt from layouts

Set.new([/\.rjs$/])
@@warn_cache_misses =

A warning will be displayed whenever an action results in a cache miss on your view paths.

false

Instance Attribute Summary collapse

Class Method Summary collapse

Instance Method Summary collapse

Constructor Details

#initialize(view_paths = [], controller = nil) ⇒ Base

:nodoc:



233
234
235
236
237
238
239
240
 
# File 'lib/reactive-mvc/view/base.rb', line 233

def initialize(view_paths = [], controller = nil)#:nodoc:
  @assigns = {}
  @assigns_added = nil
  @_render_stack = []
  @controller = controller
  @helpers = ProxyModule.new(self)
  self.view_paths = view_paths
end

Instance Attribute Details

#assigns ⇒ Object

Returns the value of attribute assigns.



163
164
165
 
# File 'lib/reactive-mvc/view/base.rb', line 163

def assigns
  @assigns
end

#base_path ⇒ Object

Returns the value of attribute base_path.



163
164
165
 
# File 'lib/reactive-mvc/view/base.rb', line 163

def base_path
  @base_path
end

#controller ⇒ Object

Returns the value of attribute controller.



164
165
166
 
# File 'lib/reactive-mvc/view/base.rb', line 164

def controller
  @controller
end

#helpers ⇒ Object (readonly)

Returns the value of attribute helpers.



220
221
222
 
# File 'lib/reactive-mvc/view/base.rb', line 220

def helpers
  @helpers
end

#output_buffer ⇒ Object

Returns the value of attribute output_buffer.



168
169
170
 
# File 'lib/reactive-mvc/view/base.rb', line 168

def output_buffer
  @output_buffer
end

#template_extension ⇒ Object

Returns the value of attribute template_extension.



163
164
165
 
# File 'lib/reactive-mvc/view/base.rb', line 163

def template_extension
  @template_extension
end

#template_format ⇒ Object

The format to be used when choosing between multiple templates with the same name but differing formats. See Request#template_format for more details.



272
273
274
275
276
277
278
279
280
 
# File 'lib/reactive-mvc/view/base.rb', line 272

def template_format
  if defined? @template_format
    @template_format
  elsif controller && controller.respond_to?(:request)
    @template_format = controller.request.format
  else
    @template_format = default_template_format
  end
end

#view_paths ⇒ Object

Returns the value of attribute view_paths.



242
243
244
 
# File 'lib/reactive-mvc/view/base.rb', line 242

def view_paths
  @view_paths
end

Class Method Details

.exempt_from_layout(*extensions) ⇒ Object

Don’t render layouts for templates with the given extensions.



195
196
197
198
199
200
 
# File 'lib/reactive-mvc/view/base.rb', line 195

def self.exempt_from_layout(*extensions)
  regexps = extensions.collect do |extension|
    extension.is_a?(Regexp) ? extension : /\.#{Regexp.escape(extension.to_s)}$/
  end
  @@exempt_from_layout.merge(regexps)
end

.format_handler_for(format) ⇒ Object 



183
184
185
 
# File 'lib/reactive-mvc/view/base.rb', line 183

def format_handler_for(format)
  @@format_handlers[format.to_sym]
end

.handle_request(request) ⇒ Object 



175
176
177
 
# File 'lib/reactive-mvc/view/base.rb', line 175

def handle_request(request)
  Dispatcher.dispatch(request)
end

.process_view_paths(value) ⇒ Object 



216
217
218
 
# File 'lib/reactive-mvc/view/base.rb', line 216

def self.process_view_paths(value)
  Reactive::Mvc::View::PathSet.new(Array(value))
end

.register_format_handler(format, handler) ⇒ Object 



179
180
181
 
# File 'lib/reactive-mvc/view/base.rb', line 179

def register_format_handler(format, handler)
  @@format_handlers[format.to_sym] = handler
end

Instance Method Details

#default_template_format ⇒ Object 



282
283
284
 
# File 'lib/reactive-mvc/view/base.rb', line 282

def default_template_format
  :rb
end

#render(options = {}, local_assigns = {}, &block) ⇒ Object

Renders the template present at template_path (relative to the view_paths array). The hash in local_assigns is made available as local variables.



250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
 
# File 'lib/reactive-mvc/view/base.rb', line 250

def render(options = {}, local_assigns = {}, &block) #:nodoc:
  local_assigns ||= {}

  if options.is_a?(String)
    render(:file => options, :locals => local_assigns)
  elsif options.is_a?(Hash)
    options = options.reverse_merge(:locals => {})
    if options[:layout]
      _render_with_layout(options, local_assigns, &block)
    elsif options[:file]
      _pick_template(options[:file]).render_template(self, options[:locals])
    elsif options[:partial]
      render_partial(options)
#          elsif options[:inline]
#            InlineTemplate.new(options[:inline], options[:type]).render(self, options[:locals])
    end
  end
end

#template ⇒ Object

Access the current template being rendered. Returns a ActionView::Template object.



288
289
290
 
# File 'lib/reactive-mvc/view/base.rb', line 288

def template
  @_render_stack.last
end

#template_exists?(template_path) ⇒ Boolean

Returns:

  • (Boolean) 


292
293
294
295
296
 
# File 'lib/reactive-mvc/view/base.rb', line 292

def template_exists?(template_path)
  _pick_template(template_path) ? true : false
rescue MissingTemplate
  false
end