radiant 0.6.6 → 0.6.7

data/vendor/plugins/haml/lib/haml/template.rb

@@ -0,0 +1,43 @@
+require 'haml/engine'
+
+module Haml
+  class Template
+    class << self
+      @@options = {}
+
+      # Gets various options for Haml. See README.rdoc for details.
+      def options
+        @@options
+      end
+
+      # Sets various options for Haml. See README.rdoc for details.
+      def options=(value)
+        @@options = value
+      end
+    end
+  end
+end
+
+# Decide how we want to load Haml into Rails.
+# Patching was necessary for versions <= 2.0.1,
+# but we can make it a normal handler for higher versions.
+if defined?(ActionView::TemplateHandler)
+  require 'haml/template/plugin'
+else
+  require 'haml/template/patch'
+end
+
+if defined?(RAILS_ROOT)
+  # Update init.rb to the current version
+  # if it's out of date.
+  #
+  # We can probably remove this as of v1.9,
+  # because the new init file is sufficiently flexible
+  # to not need updating.
+  rails_init_file = File.join(RAILS_ROOT, 'vendor', 'plugins', 'haml', 'init.rb')
+  haml_init_file = Haml.scope('init.rb')
+  if File.exists?(rails_init_file)
+    require 'fileutils'
+    FileUtils.cp(haml_init_file, rails_init_file) unless FileUtils.cmp(rails_init_file, haml_init_file)
+  end
+end

data/vendor/plugins/haml/lib/haml/template/patch.rb

@@ -0,0 +1,58 @@
+# This file makes Haml work with Rails
+# by monkeypatching the core template-compilation methods.
+# This is necessary for versions <= 2.0.1 because the template handler API
+# wasn't sufficiently powerful to deal with caching and so forth.
+
+# This module refers to the ActionView module that's part of Ruby on Rails.
+# Haml can be used as an alternate templating engine for it,
+# and includes several modifications to make it more Haml-friendly.
+# The documentation can be found
+# here[http://rubyonrails.org/api/classes/ActionView/Base.html].
+module ActionView
+  class Base # :nodoc:
+    def delegate_template_exists_with_haml(template_path)
+      template_exists?(template_path, :haml) && [:haml]
+    end
+    alias_method :delegate_template_exists_without_haml, :delegate_template_exists?
+    alias_method :delegate_template_exists?, :delegate_template_exists_with_haml
+
+    def compile_template_with_haml(extension, template, file_name, local_assigns)
+      return compile_haml(template, file_name, local_assigns) if extension.to_s == "haml"
+      compile_template_without_haml(extension, template, file_name, local_assigns)
+    end
+    alias_method :compile_template_without_haml, :compile_template
+    alias_method :compile_template, :compile_template_with_haml
+
+    def compile_haml(template, file_name, local_assigns)
+      render_symbol = assign_method_name(:haml, template, file_name)
+      locals = local_assigns.keys
+
+      @@template_args[render_symbol] ||= {}
+      locals_keys = @@template_args[render_symbol].keys | locals
+      @@template_args[render_symbol] = locals_keys.inject({}) { |h, k| h[k] = true; h }
+
+      options = Haml::Template.options.dup
+      options[:filename] = file_name || 'compiled-template'
+
+      begin
+        Haml::Engine.new(template, options).def_method(CompiledTemplates, render_symbol, *locals)
+      rescue Exception => e
+        if logger
+          logger.debug "ERROR: compiling #{render_symbol} RAISED #{e}"
+          logger.debug "Backtrace: #{e.backtrace.join("\n")}"
+        end
+
+        base_path = if defined?(extract_base_path_from)
+                      # Rails 2.0.x
+                      extract_base_path_from(file_name) || view_paths.first
+                    else
+                      # Rails <=1.2.6
+                      @base_path
+                    end
+        raise ActionView::TemplateError.new(base_path, file_name || template, @assigns, template, e)
+      end
+
+      @@compile_time[render_symbol] = Time.now
+    end
+  end
+end

data/vendor/plugins/haml/lib/haml/template/plugin.rb

@@ -0,0 +1,72 @@
+# :stopdoc:
+# This file makes Haml work with Rails
+# using the > 2.0.1 template handler API.
+
+module Haml
+  class Plugin < ActionView::TemplateHandler
+    include ActionView::TemplateHandlers::Compilable if defined?(ActionView::TemplateHandlers::Compilable)
+
+    def compile(template)
+      options = Haml::Template.options.dup
+
+      # template is a template object in Rails >=2.1.0,
+      # a source string previously
+      if template.respond_to? :source
+        options[:filename] = template.filename
+        source = template.source
+      else
+        source = template
+      end
+
+      Haml::Engine.new(source, options).send(:precompiled_with_ambles, [])
+    end
+
+    def cache_fragment(block, name = {}, options = nil)
+      @view.fragment_for(block, name, options) do
+        eval("_hamlout.buffer", block.binding)
+      end
+    end
+  end
+end
+
+if defined? ActionView::Template and ActionView::Template.respond_to? :register_template_handler
+  ActionView::Template
+else
+  ActionView::Base
+end.register_template_handler(:haml, Haml::Plugin)
+
+# In Rails 2.0.2, ActionView::TemplateError took arguments
+# that we can't fill in from the Haml::Plugin context.
+# Thus, we've got to monkeypatch ActionView::Base to catch the error.
+if ActionView::TemplateError.instance_method(:initialize).arity == 5
+  class ActionView::Base
+    def compile_template(handler, template, file_name, local_assigns)
+      render_symbol = assign_method_name(handler, template, file_name)
+
+      # Move begin up two lines so it captures compilation exceptions.
+      begin
+        render_source = create_template_source(handler, template, render_symbol, local_assigns.keys)
+        line_offset = @@template_args[render_symbol].size + handler.line_offset
+      
+        file_name = 'compiled-template' if file_name.blank?
+        CompiledTemplates.module_eval(render_source, file_name, -line_offset)
+      rescue Exception => e # errors from template code
+        if logger
+          logger.debug "ERROR: compiling #{render_symbol} RAISED #{e}"
+          logger.debug "Function body: #{render_source}"
+          logger.debug "Backtrace: #{e.backtrace.join("\n")}"
+        end
+
+        # There's no way to tell Haml about the filename,
+        # so we've got to insert it ourselves.
+        e.backtrace[0].gsub!('(haml)', file_name) if e.is_a?(Haml::Error)
+        
+        raise ActionView::TemplateError.new(extract_base_path_from(file_name) || view_paths.first, file_name || template, @assigns, template, e)
+      end
+      
+      @@compile_time[render_symbol] = Time.now
+      # logger.debug "Compiled template #{file_name || template}\n ==> #{render_symbol}" if logger
+    end
+  end
+end
+# :startdoc:

data/vendor/plugins/haml/lib/sass.rb

@@ -0,0 +1,833 @@
+dir = File.dirname(__FILE__)
+$LOAD_PATH << dir unless $LOAD_PATH.include?(dir)
+
+# = Sass (Syntactically Awesome StyleSheets)
+#
+# Sass is a meta-language on top of CSS
+# that's used to describe the style of a document
+# cleanly and structurally,
+# with more power than flat CSS allows.
+# Sass both provides a simpler, more elegant syntax for CSS
+# and implements various features that are useful
+# for creating manageable stylesheets.
+#
+# == Features
+#
+# * Whitespace active
+# * Well-formatted output
+# * Elegant input
+# * Feature-rich
+#
+# == Using Sass
+#
+# Sass can be used in several ways:
+# As a plugin for Ruby on Rails or Merb,
+# or as a standalone parser.
+# Sass is bundled with Haml,
+# so if the Haml plugin or RubyGem is installed,
+# Sass will already be installed as a plugin or gem, respectively.
+# The first step for all of these is to install the Haml gem:
+#
+#   gem install haml
+#
+# To enable it as a Rails plugin,
+# then run
+#
+#   haml --rails path/to/rails/app
+#
+# To enable Sass in Merb,
+# add
+#
+#   dependency "merb-haml"
+#
+# to config/dependencies.rb.
+#
+# Sass templates in Rails and Merb don't quite function in the same way as views,
+# because they don't contain dynamic content,
+# and so only need to be compiled when the template file has been updated.
+# By default (see options, below),
+# ".sass" files are placed in public/stylesheets/sass.
+# Then, whenever necessary, they're compiled into corresponding CSS files in public/stylesheets.
+# For instance, public/stylesheets/sass/main.sass would be compiled to public/stylesheets/main.css.
+#
+# Using Sass in Ruby code is very simple.
+# After installing the Haml gem,
+# you can use it by running <tt>require "sass"</tt>
+# and using Sass::Engine like so:
+#
+#   engine = Sass::Engine.new("#main\n  :background-color #0000ff")
+#   engine.render #=> "#main { background-color: #0000ff; }\n"
+#
+# == CSS Rules
+#
+# Rules in flat CSS have two elements:
+# the selector
+# (e.g. "#main", "div p", "li a:hover")
+# and the attributes
+# (e.g. "color: #00ff00;", "width: 5em;").
+#
+# Sass has both of these,
+# as well as one additional element: nested rules.
+#
+# === Rules and Selectors
+#
+# However, some of the syntax is a little different.
+# The syntax for selectors is the same,
+# but instead of using brackets to delineate the attributes that belong to a particular rule,
+# Sass uses two spaces of indentation.
+# For example:
+#
+#   #main p
+#     <attribute>
+#     <attribute>
+#     ...
+#
+# Like CSS, you can stretch rules over multiple lines.
+# However, unlike CSS, you can only do this if each line but the last
+# ends with a comma.
+# For example:
+#
+#   .users #userTab,
+#   .posts #postsTab
+#     <attributes>
+#
+# === Attributes
+#
+# There are two different ways to write CSS attrbibutes.
+# The first is very similar to the how you're used to writing them:
+# with a colon between the name and the value.
+# However, Sass attributes don't have semicolons at the end;
+# each attribute is on its own line, so they aren't necessary.
+# For example:
+#
+#   #main p
+#     color: #00ff00
+#     width: 97%
+#
+# is compiled to:
+#
+#   #main p {
+#     color: #00ff00;
+#     width: 97% }
+#
+# The second syntax for attributes is slightly different.
+# The colon is at the beginning of the attribute,
+# rather than between the name and the value,
+# so it's easier to tell what elements are attributes just by glancing at them.
+# For example:
+#
+#   #main p
+#     :color #00ff00
+#     :width 97%
+#
+# is compiled to:
+#
+#   #main p {
+#     color: #00ff00;
+#     width: 97% }
+#
+# By default, either attribute syntax may be used.
+# If you want to force one or the other,
+# see the <tt>:attribute_syntax</tt> option below.
+#
+# === Nested Rules
+#
+# Rules can also be nested within each other.
+# This signifies that the inner rule's selector is a child of the outer selector.
+# For example:
+#
+#   #main p
+#     :color #00ff00
+#     :width 97%
+#
+#     .redbox
+#       :background-color #ff0000
+#       :color #000000
+#
+# is compiled to:
+#
+#   #main p {
+#     color: #00ff00;
+#     width: 97%; }
+#     #main p .redbox {
+#       background-color: #ff0000;
+#       color: #000000; }
+#
+# This makes insanely complicated CSS layouts with lots of nested selectors very simple:
+#
+#   #main
+#     :width 97%
+#
+#     p, div
+#       :font-size 2em
+#       a
+#         :font-weight bold
+#
+#     pre
+#       :font-size 3em
+#
+# is compiled to:
+#
+#   #main {
+#     width: 97%; }
+#     #main p, #main div {
+#       font-size: 2em; }
+#       #main p a, #main div a {
+#         font-weight: bold; }
+#     #main pre {
+#       font-size: 3em; }
+#
+# === Referencing Parent Rules
+#
+# In addition to the default behavior of inserting the parent selector
+# as a CSS parent of the current selector
+# (e.g. above, "#main" is the parent of "p"),
+# you can have more fine-grained control over what's done with the parent selector
+# by using the ampersand character "&" in your selectors.
+#
+# The ampersand is automatically replaced by the parent selector,
+# instead of having it prepended.
+# This allows you to cleanly create pseudo-attributes:
+#
+#   a
+#     :font-weight bold
+#     :text-decoration none
+#     &:hover
+#       :text-decoration underline
+#     &:visited
+#       :font-weight normal
+#
+# Which would become:
+#
+#   a {
+#     font-weight: bold;
+#     text-decoration: none; }
+#     a:hover {
+#       text-decoration: underline; }
+#     a:visited {
+#       font-weight: normal; }
+#
+# It also allows you to add selectors at the base of the hierarchy,
+# which can be useuful for targeting certain styles to certain browsers:
+#
+#   #main
+#     :width 90%
+#     #sidebar
+#       :float left
+#       :margin-left 20%
+#       .ie6 &
+#         :margin-left 40%
+#
+# Which would become:
+#
+#   #main {
+#     width: 90%; }
+#     #main #sidebar {
+#       float: left;
+#       margin-left: 20%; }
+#       .ie6 #main #sidebar {
+#         margin-left: 40%; }
+#
+# === Attribute Namespaces
+#
+# CSS has quite a few attributes that are in "namespaces;"
+# for instance, "font-family," "font-size," and "font-weight"
+# are all in the "font" namespace.
+# In CSS, if you want to set a bunch of attributes in the same namespace,
+# you have to type it out each time.
+# Sass offers a shortcut for this:
+# just write the namespace one,
+# then indent each of the sub-attributes within it.
+# For example:
+#
+#   .funky
+#     :font
+#       :family fantasy
+#       :size 30em
+#       :weight bold
+#
+# is compiled to:
+#
+#   .funky {
+#     font-family: fantasy;
+#     font-size: 30em;
+#     font-weight: bold; }
+#
+# == Constants
+#
+# Sass has support for setting document-wide constants.
+# They're set using an exclamation mark followed by the name,
+# an equals sign, and the value.
+# An attribute can then be set to the value of a constant
+# by following it with another equals sign.
+# For example:
+#
+#   !main_color = #00ff00
+#
+#   #main
+#     :color = !main_color
+#     :p
+#       :background-color = !main_color
+#       :color #000000
+#
+# is compiled to:
+#
+#   #main {
+#     color: #00ff00; }
+#     #main p {
+#       background-color: #00ff00;
+#       color: #000000; }
+#
+# === Arithmetic
+#
+# You can even do basic arithmetic with constants.
+# Sass recognizes numbers, colors,
+# lengths (numbers with units),
+# and strings (everything that's not one of the above),
+# and various operators that work on various values.
+# All the normal arithmetic operators
+# (+, -, *, /, %, and parentheses for grouping)
+# are defined as usual
+# for numbers, colors, and lengths.
+# The "+" operator is also defined for Strings
+# as the concatenation operator.
+# For example:
+#
+#   !main_width = 10
+#   !unit1 = em
+#   !unit2 = px
+#   !bg_color = #a5f39e
+#
+#   #main
+#     :background-color = !bg_color
+#     p
+#       :background-color = !bg_color + #202020
+#       :width = !main_width + !unit1
+#     img.thumb
+#       :width = (!main_width + 15) + !unit2
+#
+# is compiled to:
+#
+#   #main {
+#     background-color: #a5f39e; }
+#     #main p {
+#       background-color: #c5ffbe;
+#       width: 10em; }
+#     #main img.thumb {
+#       width: 25em; }
+#
+# === Colors
+#
+# Colors may be written as three- or six-digit hex numbers prefixed
+# by a pound sign (#), or as HTML4 color names. For example,
+# "#ff0", "#ffff00" and "yellow" all refer to the same color.
+#
+# Not only can arithmetic be done between colors and other colors,
+# but it can be done between colors and normal numbers.
+# In this case, the operation is done piecewise one each of the
+# Red, Green, and Blue components of the color.
+# For example:
+#
+#   !main_color = #a5f39e
+#
+#   #main
+#     :background-color = !main_color
+#     p
+#       :background-color = !main_color + 32
+#
+# is compiled to:
+#
+#   #main {
+#     background-color: #a5f39e; }
+#     #main p {
+#       background-color: #c5ffbe; }
+#
+# === Strings
+#
+# Strings are the type that's used by default
+# when an element in a bit of constant arithmetic isn't recognized
+# as another type of constant.
+# However, they can also be created explicitly be wrapping a section of code with quotation marks.
+# Inside the quotation marks,
+# a backslash can be used to
+# escape quotation marks that you want to appear in the CSS.
+# For example:
+#
+#   !content = "Hello, \"Hubert\" Bean."
+#
+#   #main
+#     :content = "string(" + !content + ")"
+#
+# is compiled to:
+#
+#   #main {
+#     content: string(Hello, "Hubert" Bean.) }
+#
+# === Optional Assignment
+#
+# You can assign Sass constants if they aren't already assigned
+# using the ||= assignment operator.
+# This means that if the constant has already been assigned to,
+# it won't be re-assigned,
+# but if it doesn't have a value yet,
+# it will be given one.
+# For example:
+#
+#   !content = "First content"
+#   !content ||= "Second content?"
+#
+#   #main
+#     content = content
+#
+# is compiled to:
+#
+#   #main {
+#     content: First content; }
+#
+# However,
+#
+#   !content ||= "Second content?"
+#
+#   #main
+#     content = content
+#
+# is compiled to:
+#
+#   #main {
+#     content: Second content?; }
+#
+# === Default Concatenation
+#
+# All those plusses and quotes for concatenating strings
+# can get pretty messy, though.
+# Most of the time, if you want to concatenate stuff,
+# you just want individual values with spaces in between them.
+# Thus, in Sass, when two values are next to each other without an operator,
+# they're simply joined with a space.
+# For example:
+#
+#   !font_family = "sans-serif"
+#   !main_font_size = 1em
+#
+#   #main
+#     :font
+#       :family = !font_family
+#       :size = !main_font_size
+#     h6
+#       :font = italic "small-caps" bold (!main_font_size + 0.1em) !font_family
+#
+# is compiled to:
+#
+#   #main {
+#     font-family: sans-serif;
+#     font-size: 1em; }
+#     #main h6 {
+#       font: italic small-caps bold 1.1em sans-serif; }
+#
+# == Directives
+#
+# Directives allow the author to directly issue instructions to the Sass compiler.
+# They're prefixed with an at sign, "<tt>@</tt>",
+# followed by the name of the directive,
+# a space, and any arguments to it -
+# just like CSS directives.
+# For example:
+#
+#   @import red.sass
+#
+# === Import
+#
+# Currently, the only directive is the "import" directive.
+# It works in a very similar way to the CSS import directive,
+# and sometimes compiles to a literal CSS "@import".
+#
+# Sass can import either other Sass files or plain CSS files.
+# If it imports a Sass file,
+# not only are the rules from that file included,
+# but all constants in that file are made available in the current file.
+#
+# Sass looks for other Sass files in the working directory,
+# and the Sass file directory under Rails or Merb.
+# Additional search directories may be specified
+# using the :load_paths option (see below).
+#
+# Sass can also import plain CSS files.
+# In this case, it doesn't literally include the content of the files;
+# rather, it uses the built-in CSS "@import" directive to tell the client program
+# to import the files.
+#
+# The import directive can take either a full filename
+# or a filename without an extension.
+# If an extension isn't provided,
+# Sass will try to find a Sass file with the given basename in the load paths,
+# and, failing that, will assume a relevant CSS file will be available.
+#
+# For example,
+#
+#   @import foo.sass
+#
+# would compile to
+#
+#   .foo
+#     :color #f00
+#
+# whereas
+#
+#   @import foo.css
+#
+# would compile to
+#
+#   @import foo.css
+#
+# Finally,
+#
+#  @import foo
+#
+# might compile to either,
+# depending on whether a file called "foo.sass" existed.
+#
+# === @font-face, @media, etc.
+#
+# Sass behaves as you'd expect for normal CSS @-directives.
+# For example:
+#
+#   @font-face
+#     font-family: "Bitstream Vera Sans"
+#     src: url(http://foo.bar/bvs")
+#
+# compiles to:
+#
+#   @font-face {
+#     font-family: "Bitstream Vera Sans";
+#     src: url(http://foo.bar/bvs"); }
+#
+# and
+#
+#   @media print
+#     #sidebar
+#       display: none
+#
+#     #main
+#       background-color: white
+#
+# compiles to:
+#
+#   @media print {
+#     #sidebar {
+#       display: none; }
+#
+#     #main {
+#       background-color: white; }
+#   }
+#
+# == Comments
+#
+# === Silent Comments
+#
+# It's simple to add "silent" comments,
+# which don't output anything to the CSS document,
+# to a Sass document.
+# Simply use the familiar C-style notation for a one-line comment, "//",
+# at the normal indentation level and all text following it won't be output.
+# For example:
+#
+#   // A very awesome rule.
+#   #awesome.rule
+#     // An equally awesome attribute.
+#     :awesomeness very
+#
+# becomes
+#
+#   #awesome.rule {
+#     awesomeness: very; }
+#
+# You can also nest text beneath a comment to comment out a whole block.
+# For example:
+#
+#   // A very awesome rule
+#   #awesome.rule
+#     // Don't use these attributes
+#       color: green
+#       font-size: 10em
+#     color: red
+#
+# becomes
+#
+#   #awesome.rule {
+#     color: red; }
+#
+# === Loud Comments
+#
+# "Loud" comments are just as easy as silent ones.
+# These comments output to the document as CSS comments,
+# and thus use the same opening sequence: "/*".
+# For example:
+#
+#   /* A very awesome rule.
+#   #awesome.rule
+#     /* An equally awesome attribute.
+#     :awesomeness very
+#
+# becomes
+#
+#   /* A very awesome rule. */
+#   #awesome.rule {
+#     /* An equally awesome attribute. */
+#     awesomeness: very; }
+#
+# You can also nest content beneath loud comments. For example:
+#
+#   #pbj
+#     /* This rule describes
+#       the styling of the element
+#       that represents
+#       a peanut butter and jelly sandwich.
+#     :background-image url(/images/pbj.png)
+#     :color red
+#
+# becomes
+#
+#   #pbj {
+#     /* This rule describes
+#      * the styling of the element
+#      * that represents
+#      * a peanut butter and jelly sandwich. */
+#     background-image: url(/images/pbj.png);
+#     color: red; }
+#
+# == Mixins
+#
+# Mixins enable you to define groups of CSS attributes and
+# then include them inline in any number of selectors
+# throughout the document.
+#
+# === Defining a Mixin
+#
+# To define a mixin you use a slightly modified form of selector syntax.
+# For example the 'large-text' mixin is defined as follows:
+#
+#   =large-text
+#     :font
+#       :family Arial
+#       :size 20px
+#       :weight bold
+#     :color #ff0000
+#
+# The initial '=' marks this as a mixin rather than a standard selector.
+# The CSS rules that follow won't be included until the mixin is referenced later on.
+# Anything you can put into a standard selector,
+# you can put into a mixin definition. e.g.
+#
+#   =clearfix
+#     display: inline-block
+#     &:after
+#       content: "."
+#       display: block
+#       height: 0
+#       clear: both
+#       visibility: hidden
+#     * html &
+#       height: 1px
+#
+#
+# === Mixing it in
+#
+# Inlining a defined mixin is simple,
+# just prepend a '+' symbol to the name of a mixin defined earlier in the document.
+# So to inline the 'large-text' defined earlier,
+# we include the statment '+large-text' in our selector definition thus:
+#
+#   .page-title
+#     +large-text
+#     :padding 4px
+#     :margin
+#       :top 10px
+#
+#
+# This will produce the following CSS output:
+#
+#   .page-title {
+#     font-family: Arial;
+#     font-size: 20px;
+#     font-weight: bold;
+#     color: #ff0000;
+#     padding: 4px;
+#     margin-top: 10px;
+#   }
+#
+# Any number of mixins may be defined and there is no limit on
+# the number that can be included in a particular selector.
+#
+# Mixin definitions can also include references to other mixins defined earlier in the file.
+# E.g.
+#
+#   =highlighted-background
+#     background:
+#       color: #fc0
+#   =header-text
+#     font:
+#       size: 20px
+#
+#   =compound
+#     +highlighted-background
+#     +header-text
+#
+#
+# == Output Style
+#
+# Although the default CSS style that Sass outputs is very nice,
+# and reflects the structure of the document in a similar way that Sass does,
+# sometimes it's good to have other formats available.
+#
+# Sass allows you to choose between three different output styles
+# by setting the <tt>:style</tt> option.
+# In Rails, this is done by setting <tt>Sass::Plugin.options[:style]</tt>;
+# outside Rails, it's done by passing an options hash with </tt>:style</tt> set.
+#
+# === <tt>:nested</tt>
+#
+# Nested style is the default Sass style,
+# because it reflects the structure of the document
+# in much the same way Sass does.
+# Each attribute has its own line,
+# but the indentation isn't constant.
+# Each rule is indented based on how deeply it's nested.
+# For example:
+#
+#   #main {
+#     color: #fff;
+#     background-color: #000; }
+#     #main p {
+#       width: 10em; }
+#
+#   .huge {
+#     font-size: 10em;
+#     font-weight: bold;
+#     text-decoration: underline; }
+#
+# Nested style is very useful when looking at large CSS files
+# for the same reason Sass is useful for making them:
+# it allows you to very easily grasp the structure of the file
+# without actually reading anything.
+#
+# === <tt>:expanded</tt>
+#
+# Expanded is the typical human-made CSS style,
+# with each attribute and rule taking up one line.
+# Attributes are indented within the rules,
+# but the rules aren't indented in any special way.
+# For example:
+#
+#   #main {
+#     color: #fff;
+#     background-color: #000;
+#   }
+#   #main p {
+#     width: 10em;
+#   }
+#
+#   .huge {
+#     font-size: 10em;
+#     font-weight: bold;
+#     text-decoration: underline;
+#   }
+#
+# === <tt>:compact</tt>
+#
+# Compact style, as the name would imply,
+# takes up less space than Nested or Expanded.
+# However, it's also harder to read.
+# Each CSS rule takes up only one line,
+# with every attribute defined on that line.
+# Nested rules are placed next to each other with no newline,
+# while groups of rules have newlines between them.
+# For example:
+#
+#   #main { color: #fff; background-color: #000; }
+#   #main p { width: 10em; }
+#
+#   .huge { font-size: 10em; font-weight: bold; text-decoration: underline; }
+#
+# === <tt>:compressed</tt>
+#
+# Compressed style takes up the minimum amount of space possible,
+# having no whitespace except that necessary to separate selectors
+# and a newline at the end of the file.
+# It's not meant to be human-readable.
+# For example:
+#
+#   #main{color:#fff;background-color:#000}#main p{width:10em}.huge{font-size:10em;font-weight:bold;text-decoration:underline}
+#
+# == Sass Options
+#
+# Options can be set by setting the hash <tt>Sass::Plugin.options</tt>
+# from <tt>environment.rb</tt> in Rails,
+# or by passing an options hash to Sass::Engine.
+# Available options are:
+#
+# [<tt>:style</tt>]             Sets the style of the CSS output.
+#                               See the section on Output Style, above.
+#
+# [<tt>:attribute_syntax</tt>]  Forces the document to use one syntax for attributes.
+#                               If the correct syntax isn't used, an error is thrown.
+#                               <tt>:normal</tt> forces the use of a colon
+#                               before the attribute name.
+#                               For example: <tt>:color #0f3</tt>
+#                               or <tt>:width = !main_width</tt>.
+#                               <tt>:alternate</tt> forces the use of a colon or equals sign
+#                               after the attribute name.
+#                               For example: <tt>color: #0f3</tt>
+#                               or <tt>width = !main_width</tt>.
+#                               By default, either syntax is valid.
+#
+# [<tt>:never_update</tt>]      Whether the CSS files should never be updated,
+#                               even if the template file changes.
+#                               Setting this to true may give small performance gains.
+#                               It always defaults to false.
+#                               Only has meaning within Ruby on Rails or Merb.
+#
+# [<tt>:always_update</tt>]     Whether the CSS files should be updated every
+#                               time a controller is accessed,
+#                               as opposed to only when the template has been modified.
+#                               Defaults to false.
+#                               Only has meaning within Ruby on Rails or Merb.
+#
+# [<tt>:always_check</tt>]      Whether a Sass template should be checked for updates every
+#                               time a controller is accessed,
+#                               as opposed to only when the Rails server starts.
+#                               If a Sass template has been updated,
+#                               it will be recompiled and will overwrite the corresponding CSS file.
+#                               Defaults to false in production mode, true otherwise.
+#                               Only has meaning within Ruby on Rails or Merb.
+#
+# [<tt>:full_exception</tt>]    Whether an error in the Sass code
+#                               should cause Sass to provide a detailed description.
+#                               If set to true, the specific error will be displayed
+#                               along with a line number and source snippet.
+#                               Otherwise, a simple uninformative error message will be displayed.
+#                               Defaults to false in production mode, true otherwise.
+#                               Only has meaning within Ruby on Rails or Merb.
+#
+# [<tt>:template_location</tt>] The directory where Sass templates should be read from.
+#                               Defaults to <tt>RAILS_ROOT + "/public/stylesheets/sass"</tt>
+#                               or <tt>MERB_ROOT + "/public/stylesheets/sass"</tt>.
+#                               Only has meaning within Ruby on Rails or Merb.
+#
+# [<tt>:css_location</tt>]      The directory where CSS output should be written to.
+#                               Defaults to <tt>RAILS_ROOT + "/public/stylesheets"</tt>
+#                               or <tt>MERB_ROOT + "/public/stylesheets"</tt>.
+#                               Only has meaning within Ruby on Rails or Merb.
+#
+# [<tt>:filename</tt>]          The filename of the file being rendered.
+#                               This is used solely for reporting errors,
+#                               and is automatically set when using Rails or Merb.
+#
+# [<tt>:load_paths</tt>]        An array of filesystem paths which should be searched
+#                               for Sass templates imported with the "@import" directive.
+#                               This defaults to the working directory and, in Rails or Merb,
+#                               whatever <tt>:template_location</tt> is.
+#
+module Sass; end
+
+require 'sass/engine'
+require 'sass/plugin' if defined?(Merb::Plugins)