scotch-view_fu 0.9.1

data/MIT-LICENSE

@@ -0,0 +1,40 @@
+ViewFu - Copyright (c) 2008 NeoRails.com 
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+Original Plugins (Styler, Javascripter, Headliner) - Copyright (c) 2007 Patrick Crowley, the.railsi.st
+	
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README

@@ -0,0 +1,145 @@
+ViewFu
+======
+
+ViewFu is a Rails plugin that provides all the miscellaneous View tasks. It's a combination of the functionality of Styler, Javascripter, and Headline (from Patrick Crowley, the.railsi.st) - along with additional tweaks such as providing commonly used View Helpers Methods.
+
+
+Maintainer Info
+======
+
+Tyler Crocker
+NeoRails.com
+
+Looking for *the one* awesome rails developer to add to your project? I may be available to help out. Contact me at neorails@gmail.com. 
+
+
+ViewFu HTML Helpers
+=======
+ViewFu provides helpers for commonly used html elements
+
+br #=> <br />
+hr #=> <hr />
+anchor("posts") #=> <a name='posts'></a>
+clear #=> <div class="clear"></div>
+clear(:left) #=> <div class="clearleft"></div>
+clear_tag(:br) #=> <br class="clear" />
+lorem #=> Lorem ipsum dolor...
+
+
+ViewFu Helper Queries
+=======
+production? #=> returns true if Rails.env == "production"
+is_new? #=> returns true is we're on a "new" or "create" action
+is_edit? #=> returns true is we're on an "edit" or "update" action
+use_cache? #=> returns true if perform_caching is turned on
+
+
+ViewFu Misc Helpers
+=======
+paging(@array) #=> display a will_paginate paging links (only if the array is a valid paging collection)
+paging(@array, :sabros) #=> wrap the paging links with a class "sabros"
+
+
+Haml Specific Helpers
+=======
+Haml allows you to pash a hash of attributes. ViewFu assists this by providing a simple "hidden" helper that allows you to conditionally hide page elements.
+
+%div{hidden} #=> <div style="display:none">
+%div.posts{hidden_if(@posts.empty?)} #=> hide the .posts div if the array is empty
+%p.empty{hidden_unless(@posts.empty?)} #=> hide the empty posts message if the array has elements
+
+
+Stylesheets
+=======
+ViewFu allows you to add a dynamic stylesheets collection to the top of your page. If you have any partials that depend on a stylesheet, they just need to call add_stylesheet(path) and the styles will be available on the page. 
+
+You'll just need to add a call *stylesheets* somewhere your page header. 
+
+stylesheets
+writes the stylesheet collection to html
+
+stylesheet
+alias around stylesheet_link_tag
+
+stylesheet_folder(path) 
+lets you include a recursive folder of stylesheets
+
+page_stylesheets
+output stylesheets specific to a page
+
+add_stylesheet(path)
+adds a stylesheet to the collection to be included on the page
+
+ignore_stylesheet(path)
+removes a stylesheet from the collection to be included on the page
+
+See lib/stylesheet/README for more details
+
+
+Javascripts
+=======
+ViewFu allows you to add a dynamic javascript collection to the top(or bottom) of your page. Now, if you have a partial that depends on a javascript library, you can just include it via add_javascript(path) and it will appear on the top of your page.
+
+You'll just need add a call to *javascripts* to your layout and the javascripts you included an all your partials will appear.
+
+javascripts
+writes the javascript collection to html
+
+javascript
+alias around javascript_include_tag
+
+javascript_folder(path) 
+lets you include a recursive folder of javascripts
+
+page_javascripts
+output javascripts specific to a page
+
+add_javascript(path)
+adds a javascript to the collection to be included on the page
+
+ignore_javascript(path)
+removes a javascript from the collection to be included on the page
+
+See lib/javascripter/README for more details
+
+Page Titles
+=======
+ViewFu allows you to easily set the current page title from anywhere on your views
+
+title
+Displays the current page title
+
+title(new_title)
+Sets the page title
+
+See lib/headliner/README for more details
+
+
+Meta Tags
+=======
+ViewFu allows you to set meta tags on your page header from anywhere. Just add a call to meta_tags somewhere in your page header.
+
+meta_tags
+output all the html meta tags currently on the page
+
+meta_keywords
+output the meta keywords tag
+
+meta_keywords(val)
+set the page meta keywords
+
+meta_description
+output the meta description tag
+
+meta_description(val)
+set the page meta description
+
+
+More Plugins
+======
+
+If you like ViewFu, you'll *love* FormFu. It provides a beautiful way to generate tableless Rails html forms. Works just like form_for, except it'll generate the entire XHTML (label, wrapper, validation message, etc). 
+https://github.com/neorails/form_fu
+
+
+Copyright (c) 2008 NeoRails.com, released under the MIT license

data/Rakefile

@@ -0,0 +1,22 @@
+require 'rake'
+require 'rake/testtask'
+require 'rake/rdoctask'
+
+desc 'Default: run unit tests.'
+task :default => :test
+
+desc 'Test the view_fu plugin.'
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'lib'
+  t.pattern = 'test/**/*_test.rb'
+  t.verbose = true
+end
+
+desc 'Generate documentation for the view_fu plugin.'
+Rake::RDocTask.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title    = 'ViewFu'
+  rdoc.options << '--line-numbers' << '--inline-source'
+  rdoc.rdoc_files.include('README')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end

data/init.rb

@@ -0,0 +1 @@
+require File.dirname(__FILE__) + "/rails/init"

data/lib/browser_detect/helper.rb

@@ -0,0 +1,45 @@
+module BrowserDetect::Helper
+  
+  # check the current browser (via user agent) for the following:
+  # :mozilla
+  # :ie6
+  # :ie7
+  # :ie
+  # :safari
+  def browser_is? name
+
+    name = name.to_s.strip
+
+    return true if browser_name == name
+    return true if name == 'mozilla' && browser_name == 'gecko'
+    return true if name == 'ie6' && browser_name.index('ie6')
+    return true if name == 'ie7' && browser_name.index('ie7')
+    return true if name == 'ie' && browser_name.index('ie')
+    return true if name == 'webkit' && browser_name == 'safari'
+
+  end
+  
+  # find the current browser name
+  def browser_name
+    @browser_name ||= begin
+
+      ua = request.env['HTTP_USER_AGENT'].to_s.downcase
+
+      if ua.index('msie') && !ua.index('opera') && !ua.index('webtv')
+        'ie'+ua[ua.index('msie')+5].chr
+      elsif ua.index('gecko/') 
+        'gecko'
+      elsif ua.index('opera')
+        'opera'
+      elsif ua.index('konqueror') 
+        'konqueror'
+      elsif ua.index('applewebkit/')
+        'safari'
+      elsif ua.index('mozilla/')
+        'gecko'
+      else
+        ""
+      end
+    end
+  end
+end

data/lib/headliner/README

@@ -0,0 +1,118 @@
+=========
+Headliner
+=========
+
+Headliner DRYs up your page titles.
+
+
+Background
+==========
+
+Normally, if your Rails application has lots of actions and a shared
+layout, you might find yourself setting custom page title names in your
+controllers.
+
+Here's an example:
+
+class PagesController < ApplicationController
+  def about
+    @title = "About us"
+  end
+end
+
+Then, in your main layout, you might have something like this:
+
+<head>
+<title>My website<% if @title %>: <%= @title %><% end %></title>
+</head
+
+This works okay... but page titles don't really belong in controllers, do
+they?
+
+So, by moving these titles into your views, we can DRY things up a bit and
+reinforce the MVC design pattern that's so fundamental to Ruby on Rails.
+
+
+Usage
+=====
+
+First, add this code to your main layout:
+
+<head>
+<%= title :site => "My website" %>
+</head>
+
+Then, to set the page title, add this to each of your views:
+
+<h1><%= title "My page title" %></h1>
+
+When views are rendered, the page title will be included in the right
+spots:
+
+<head>
+<title>My website | My page title</title>
+</head>
+<body>
+<h1>My page title</h1>
+</body>
+
+
+Options
+=======
+
+Use these options to customize the title format:
+
+:prefix (text between site name and separator)
+:separator (text used to separate website name from page title)
+:suffix (text between separator and page title)
+:lowercase (when true, the page name will be lowercase)
+:reverse (when true, the page and site names will be reversed)
+
+And here are a few examples to give you ideas.
+
+<%= title :separator => "&mdash;" %>
+<%= title :prefix => false, :separator => ":" %>
+<%= title :lowercase => true %>
+<%= title :reverse => true, :prefix => false %>
+
+
+Dealing with special pages
+==========================
+
+How do you set the page title without showing it in the view?
+
+<% title "My page title" %>
+
+What if your view headline is different from your page title?
+
+<%= title "My page title", "My headline" %>
+
+
+Mr. T says, ‘Use my method, fool!’
+==================================
+
+Just like ERB's HTML safe method, you can invoke Headliner with a single
+letter alias.
+
+<h1><%=t "My page title" %></h1>
+
+
+How does it work?
+=================
+
+Ruby on Rails renders actions *before* inserting them into layouts. So, if 
+you set a variable in your view, it will be accessible in your layout. But, 
+at first glance, it looks like you're using a variable (in the head)
+before it's been assigned a value (in the body). Cool, huh?
+
+
+Credits
+=======
+
+Special thanks to Nick Zadrozny and Jordan Fowler for their input.
+
+
+Feedback
+========
+
+Comments, bug reports, and svn diffs welcome at http://the.railsi.st.

data/lib/headliner/helper.rb

@@ -0,0 +1,65 @@
+module Headliner
+  module Helper
+    def title(options, headline='')
+      if options.is_a? String
+        save_title(options, headline)
+      else
+        display_title(options)
+      end
+    end
+
+    def save_title(title, headline)
+      @title = title.gsub(/<\/?[^>]*>/, '')
+      headline.blank? ? title : headline
+    end
+
+    def display_title(options)
+      # Prefix (leading space)
+      if options[:prefix]
+        prefix = options[:prefix]
+      elsif options[:prefix] == false
+        prefix = ''
+      else
+        prefix = ' '
+      end
+
+      # Separator
+      unless options[:separator].blank?
+        separator = options[:separator]
+      else
+        separator = '|'
+      end
+
+      # Suffix (trailing space)
+      if options[:suffix]
+        suffix = options[:suffix]
+      elsif options[:suffix] == false
+        suffix = ''
+      else
+        suffix = ' '
+      end
+
+      # Lowercase title?
+      if options[:lowercase] == true
+        @title = @title.downcase unless @title.blank?
+      end
+
+      # Set website/page order
+      unless @title.blank?
+        if options[:reverse] == true
+          # Reverse order => "Page : Website"
+          return content_tag(:title, @title + prefix + separator + suffix + options[:site])
+        else
+          # Standard order => "Website : Page"
+          return content_tag(:title, options[:site] + prefix + separator + suffix + @title)
+        end
+      end
+  
+      # If title is blank, return only website name
+      content_tag :title, options[:site]
+    end
+
+    # Mr. T says, "Use my method, fool!"
+    alias t title
+  end
+end

data/lib/javascripter/README

@@ -0,0 +1,87 @@
+======
+Javascripter
+======
+
+Javascripter is designed to DRY up the process of including and generating
+javascripts, so you can think less about javascript configuration and more
+about scripting.
+
+
+Usage
+=====
+
+To use Javascripter, just update your layout(s) with this code:
+
+<head>
+<title>the.rails.ist</title>
+<%= javascripts %>
+</head>
+
+Javascripter will then include your javascripts automatically:
+
+<head>
+	<title>the.rails.ist</title>
+	<link href="/javascripts/application.js?1170968897" />
+</head>
+
+Javascripter will also dynamically include javascripts for each of your
+controllers (if such javascripts are present), so you can keep your scripts
+organized into logical sections.
+
+
+Organize your javascripts
+=========================
+
+Javascripter uses a simple set of conventions:
+
+- Javascripts for your entire application should be stored in application.js
+- Javascripts for specific controllers should be stored in controller.js
+- Javascripts for specific actions should be stored in controller_action.js
+
+When used in combination, these conventions can scale up to support pretty
+big applications.
+
+
+Include additional javascripts
+==============================
+
+Conventions are great, but need to add your own javascripts?
+
+<%= javascripts :include => "reset" %>
+<%= javascripts :include => ["reset", "fonts"] %>
+
+
+Use nested javascripts (optional)
+=================================
+
+For bigger projects, you might wish to break your javascripts into separate 
+directories.
+
+To use nested javascripts, just create subdirectories in public/javascripts 
+for each of your controllers, and then add javascripts for individual 
+actions you wish to script.
+
+- Javascripts for an entire controller should be stored in controller.js
+- Javascripts for specific actions should be stored in controller/action.js
+
+
+Generator
+=========
+
+Javascripter also includes a generator that will create a default set of
+javascripts (application.js) and a separate
+javascript for each controller in your application.
+
+To use the generator, run this command in your terminal:
+
+script/generate javascripts
+
+If you add a new controller, just run the generator again and a new
+javascript for the controller will be created. (Javascripter will safely ignore
+any existing javascripts.)
+
+
+Feedback
+========
+
+Comments, bug reports, and svn diffs welcome at http://the.railsi.st.