refinerycms 0.9.7.15 → 0.9.8

data/vendor/plugins/themes/generators/refinery_theme/README

@@ -1,17 +0,0 @@
-== Refinery Theme Generator
-
-== Description
-
-Generate a new barebones Refinery theme.
-
-If you want this new theme to be the current theme used, set the "theme"
-setting in the Refinery backend to the name of this theme.
-
-== Usage
-./script/generate refinery_theme theme_name
-
-== Example
-./script/generate refinery_theme modern
-
-Results in:
-create  /themes/modern/...

data/vendor/plugins/themes/generators/refinery_theme/Rakefile

@@ -1,11 +0,0 @@
-require 'rake'
-require 'rake/testtask'
-require 'rake/rdoctask'
-
-desc 'Generate documentation for the Refinery Theme Generator plugin.'
-Rake::RDocTask.new(:rdoc) do |rdoc|
-  rdoc.rdoc_dir = 'rdoc'
-  rdoc.title    = 'Refinery Theme Generator'
-  rdoc.options << '--line-numbers' << '--inline-source'
-  rdoc.rdoc_files.include('README')
-end

data/vendor/plugins/themes/generators/refinery_theme/USAGE

@@ -1,2 +0,0 @@
-Usage:
-  ruby script/generate refinery_theme modern

data/vendor/plugins/themes/generators/refinery_theme/install.rb

@@ -1,2 +0,0 @@
-# install.rb
-puts IO.read(File.join(File.dirname(__FILE__), 'README'))

data/vendor/plugins/themes/generators/refinery_theme/refinery_theme_generator.rb

@@ -1,46 +0,0 @@
-class RefineryThemeGenerator < Rails::Generator::Base
-
-  def banner
-    "Usage: ruby script/generate refinery_theme theme_name"
-  end
-
-  def manifest
-    if @args[0].nil?
-      puts "You must specify a theme name."
-      puts banner
-      exit
-    end
-
-    record do |m|
-      m.directory "themes"
-      m.directory "themes/#{theme_name}"
-      m.directory "themes/#{theme_name}/javascripts"
-
-      m.directory "themes/#{theme_name}/stylesheets"
-      m.file "stylesheets/application.css", "themes/#{theme_name}/stylesheets/application.css"
-      m.file "stylesheets/formatting.css", "themes/#{theme_name}/stylesheets/formatting.css"
-      m.file "stylesheets/home.css", "themes/#{theme_name}/stylesheets/home.css"
-
-      m.directory "themes/#{theme_name}/views"
-      m.directory "themes/#{theme_name}/views/layouts"
-      m.file "views/layouts/application.html.erb", "themes/#{theme_name}/views/layouts/application.html.erb"
-
-      m.directory "themes/#{theme_name}/views/pages"
-      m.file "views/pages/show.html.erb", "themes/#{theme_name}/views/pages/show.html.erb"
-      m.file "views/pages/home.html.erb", "themes/#{theme_name}/views/pages/home.html.erb"
-
-      m.directory "themes/#{theme_name}/views/shared"
-      ["content_page", "footer", "head", "header", "menu", "menu_branch"].each do |partial|
-        m.file "../../../../refinery/app/views/shared/_#{partial}.html.erb","themes/#{theme_name}/views/shared/_#{partial}.html.erb"
-      end
-
-      puts 'NOTE: If you want this new theme to be the current theme used, set the "theme"
-            setting in the Refinery backend to the name of this theme.' unless RAILS_ENV == "test"
-    end
-  end
-
-  def theme_name
-    @args[0]
-  end
-
-end

data/vendor/plugins/themes/generators/refinery_theme/templates/stylesheets/application.css

@@ -1,5 +0,0 @@
-@import url('/stylesheets/refinery/application.css');
-/*
-    Override default refinery application CSS below.
-    Formatting applies to all frontend.
-*/

data/vendor/plugins/themes/generators/refinery_theme/templates/stylesheets/formatting.css

@@ -1,7 +0,0 @@
-@import url('/stylesheets/refinery/formatting.css');
-/*  
-    Override default refinery formatting below. 
-    Formatting applies to backend WYSIWYG editors and all frontend. 
-    This is the best place to put your heading and text related styles
-    like colours, fonts and line-height.
-*/

data/vendor/plugins/themes/generators/refinery_theme/templates/stylesheets/home.css

@@ -1,5 +0,0 @@
-@import url('/stylesheets/refinery/home.css');
-/* 
-    Override default refinery homepage styles here. 
-    These only apply to the homepage of your site. 
-*/

data/vendor/plugins/themes/generators/refinery_theme/templates/views/layouts/application.html.erb

@@ -1,21 +0,0 @@
-<!DOCTYPE html>
-<html>
-  <%= render :partial => "/shared/head", :locals => {:theme => true} %>
-  <body>
-    <%= render :partial => "/shared/site_bar" %>
-    <div id='page_container'>
-      <div id='page'>
-        <%= render :partial => "/shared/ie6check" if request.env['HTTP_USER_AGENT'] =~ /MSIE/ -%>
-        <div id='header'>
-          <%= render :partial => "/shared/header" %>
-        </div>
-        <div id='body' class='clearfix'>
-          <%= yield %>
-        </div>
-        <div id='footer'>
-          <%= render :partial => "/shared/footer" %>
-        </div>
-      </div>
-    </div>
-  </body>
-</html>

data/vendor/plugins/themes/generators/refinery_theme/templates/views/pages/home.html.erb

@@ -1,4 +0,0 @@
-<%# For the best way to modify this page with your own markup read %>
-<%# http://github.com/resolve/refinerycms/blob/rails2-stable/vendor/plugins/themes/readme.md %>
-
-<%= render :partial => "/shared/content_page" %>

data/vendor/plugins/themes/generators/refinery_theme/templates/views/pages/show.html.erb

@@ -1,4 +0,0 @@
-<%# For the best way to modify this page with your own markup read %>
-<%# http://github.com/resolve/refinerycms/blob/rails2-stable/vendor/plugins/themes/readme.md %>
-
-<%= render :partial => "/shared/content_page" %>

data/vendor/plugins/themes/lib/theme.rb

@@ -1,7 +0,0 @@
-class Theme
-
-  def self.current_theme(env)
-    RefinerySetting[:theme]
-  end
-
-end

data/vendor/plugins/themes/lib/theme_server.rb

@@ -1,30 +0,0 @@
-# Allow the metal piece to run in isolation
-require(File.dirname(__FILE__) + "/../../config/environment") unless defined?(Rails)
-
-# Serves theme files from the theme directory without touching Rails too much
-class ThemeServer
-
-  def initialize(app)
-    @app = app
-  end
-
-  def call(env)
-    if env["PATH_INFO"] =~ /^\/theme\/(stylesheets|javascripts|images)/ and (theme = Theme.current_theme(env)).present?
-      env["PATH_INFO"].gsub!(/^\/theme\//, '')
-      if (file_path = (dir = Rails.root.join("themes", theme)).join(env["PATH_INFO"])).exist?
-        etag = Digest::MD5.hexdigest("#{file_path.to_s}#{file_path.mtime}")
-        unless (etag == env["HTTP_IF_NONE_MATCH"])
-          status, headers, body = Rack::File.new(dir).call(env)
-          [status, headers.update({"ETag" => etag}), body]
-        else
-          [304, {"ETag" => etag}, []]
-        end
-      else
-        [404, {}, []]
-      end
-    else
-      @app.call(env)
-    end
-  end
-
-end

data/vendor/plugins/themes/rails/init.rb

@@ -1,36 +0,0 @@
-# Set up middleware to serve theme files
-config.middleware.use "ThemeServer"
-::Refinery::ApplicationController.module_eval do
-
-  # Add or remove theme paths to/from Refinery application
-  prepend_before_filter :attach_theme_to_refinery
-
-  def attach_theme_to_refinery
-    # remove any paths relating to any theme.
-    view_paths.reject! { |v| v.to_s =~ %r{^themes/} }
-
-    # add back theme paths if there is a theme present.
-    if (theme = Theme.current_theme(request.env)).present?
-      # Set up view path again for the current theme.
-      view_paths.unshift Rails.root.join("themes", theme, "views").to_s
-
-      # Ensure that routes within the application are top priority.
-      # Here we grab all the routes that are under the application's view folder
-      # and promote them ahead of any other path.
-      view_paths.select{|p| p.to_s =~ /^app\/views/}.each do |app_path|
-        view_paths.unshift app_path
-      end
-    end
-
-    # Set up menu caching for this theme or lack thereof
-    if RefinerySetting.table_exists? and
-        RefinerySetting[:refinery_menu_cache_action_suffix] != (suffix = "#{"#{theme}_" if theme.present?}site_menu")
-      RefinerySetting[:refinery_menu_cache_action_suffix] = suffix
-    end
-  end
-  protected :attach_theme_to_refinery
-
-end
-
-# Include theme functions into application helper.
-Refinery::ApplicationHelper.send :include, ThemesHelper

data/vendor/plugins/themes/readme.md

@@ -1,118 +0,0 @@
-# Themes
-
-## Introduction
-
-__Themes allow you to wrap up the design of your Refinery site into a single folder that is portable.__
-
-Refinery doesn't force you to learn a special templating language, but rather just uses the regular
-ERB views you're used to in Rails. This means creating a theme from your existing site is extremely easy.
-
-Think of a theme as your ``app/views`` directory with a few extra things like images, css and javascript.
-
-It's worth noting you don't need to use a theme if you don't want to. Placing files in the ``app/views`` directory like any other Rails app will work just fine. It's only if you want to wrap your design up into a single location that you would use a theme or allow your client to easily change between designs.
-
-## The Structure of a Theme
-
-Themes sit in your Rails app like this
-
-    app/
-    config/
-    db/
-    lib/
-    public/
-    themes/
-      |- mytheme/
-      |- othertheme/
-    plugins/
-    tests/
-
-Let's take the ``mytheme`` example theme shown above. This is how the theme is structured:
-
-    mytheme/
-       |- images
-       |    |- whatever.png
-       |    |- foo.jpg
-       |- javascripts
-       |    |- whatever.js
-       |- LICENSE
-       |- README
-       |- stylesheets/
-       |    |- application.css
-       |    |- whatever.css
-       |- views
-            |- pages
-            |    |- show.html.erb
-            |    |- index.html.erb
-            |- layouts
-                 |- application.html.erb
-
-   
-### Images
-
-Usually this would be just what you have in ``public/images`` except we move that to the theme instead.
-
-### Javascripts
-
-Same with javascripts, just what you normally have in ``public/javascripts`` but in this theme directory instead.
-
-### Readme
-
-The ``README`` file is just a description of your theme.
-
-### Views
-
-This is exactly the same as how you lay your views out in ``app/views/`` just instead of putting them in ``app/views/`` you put them into ``themes/mytheme/views/``
-
-## How do I make my own Theme?
-
-Simply use the Theme generator to make the basic structure of a new theme.
-
-    ruby script/generate refinery_theme name_of_theme
-
-Don't forget to "activate" this new theme by setting the theme setting to the name of this new theme.
-
-## How do I select which Theme Refinery should use?
-
-In the admin area of Refinery go to the "Settings" area, locate the setting called "theme" and edit it.
-
-Set the value of that setting to the name of your themes folder. For example, if your theme is sitting in:
-
-    themes/my_theme
-
-set it to ``my_theme`` and hit save.
-
-## How do I install someone else's Theme?
-
-Just copy their theme directory into your themes folder and Refinery will see it.
-
-## How can I Convert my Current Views into a Theme?
-
-This should be fairly straightforward, just follow the directory structure outlined in 'The structure of a Theme'. 
-
-But there is one important difference that need to be addressed to convert your current site into a theme.
-
-If you have some CSS which refers to an image or URL:
-
-    #footer {
-      background: url('/images/footer_background.png') repeat-x;
-    }
-
-You need to update the URL so it requests ``/theme/images/`` instead of just ``/images``. This tells Refinery we need to actually load this image from the theme and not just the public directory.
-
-So the result is simply:
-
-    #footer {
-      background: url('/theme/images/footer_background.png') repeat-x;
-    }
-
-This is the same with linking to Javascript and Stylesheets in your view. Say our ``application.html.erb`` layout had something like this:
-
-    <%= stylesheet_link_tag 'application' %>
-
-You just need to change that to:
-
-    <%= stylesheet_link_tag 'application', :theme => true %>
-    
-## I'm Stuck, is there an Example Theme?
-
-Yep, there is an example theme called "demolicious" that comes with Refinery located in ``/themes/demolicious``. If you find yourself getting stuck, just check out that theme and get a feel for how it works.

data/vendor/plugins/translate/MIT-LICENSE

@@ -1,20 +0,0 @@
-Copyright (c) 2009 [name of plugin creator]
-
-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/vendor/plugins/translate/README

@@ -1,61 +0,0 @@
-Translate
-=========
-
-This plugin provides a web interface for translating Rails I18n texts (requires Rails 2.2 or higher) from one locale to another. The plugin has been tested only with the simple I18n backend that ships with Rails. I18n texts are read from and written to YAML files under config/locales.
-
-To translate to a new locale you need to add a YAML file for that locale that contains the locale as the top key and at least one translation.
-
-Please note that there are certain I18n keys that map to Array objects rather than strings and those are currently not dealt with by the translation UI. This means that Rails built in keys such as date.day_names need to be translated manually directly in the YAML file.
-
-To get the translation UI to write the YAML files in UTF8 you need to install the ya2yaml gem.
-
-The translation UI finds all I18n keys by extracting them from I18n lookups in your application source code. In addition it adds all :en and default locale keys from the I18n backend.
-
-- Updated: Each string in the UI now has an "Auto Translate" link which will send the original text to Google Translate and will input the returned translation into the form field for further clean up and review prior to saving.
-
-
-Rake Tasks
-=========
-
-In addition to the web UI this plugin adds the following rake tasks:
-
-translate:lost_in_translation
-translate:merge_keys
-translate:google
-translate:changed
-
-The lost_in_translation task shows you any I18n keys in your code that are do not have translations in the YAML file for your default locale, i.e. config/locales/sv.yml.
-
-The merge_keys task is supposed to be used in conjunction with Sven Fuch's Rails I18n TextMate bundle (http://github.com/svenfuchs/rails-i18n/tree/master). Texts and keys extracted with the TextMate bundle end up in the temporary file log/translations.yml. When you run the merge_keys rake task the keys are moved over to the corresponding I18n locale file, i.e. config/locales/sv.yml. The merge_keys task also checks for overwrites of existing keys by warning you that one of your extracted keys already exists with a different translation.
-
-The google task is used for auto translating from one locale to another using Google Translate.
-
-The changed rake task can show you between one YAML file to another which keys have had their texts changed.
-
-Installation
-=========
-Obtain the source with:
-
-./script/plugin install git://github.com/newsdesk/translate.git 
-
-To mount the plugin, add the following to your config/routes.rb file:
-
-Translate::Routes.translation_ui(map) if RAILS_ENV != "production"
-
-Now visit /translate in your web browser to start translating.
-
-Dependencies
-=========
-
-- Rails 2.2 or higher
-- The ya2yaml gem if you want your YAML files written in UTF8 encoding.
-
-Authors
-=========
-
-- Peter Marklund (programming)
-- Joakim Westerlund (web design)
-
-Many thanks to http://newsdesk.se for sponsoring the development of this plugin.
-
-Copyright (c) 2009 Peter Marklund, released under the MIT license

data/vendor/plugins/translate/REFINERY_README

@@ -1,8 +0,0 @@
-Installed from moretea/translate
-script/plugin install git://github.com/moretea/translate.git
-
-This is handy for translating refinery to other languages.
-
-  $ rake translate:lost_in_translation LOCALE=nl
-
-Run this task to get a list of missing translations

data/vendor/plugins/translate/Rakefile

@@ -1,11 +0,0 @@
-require 'rake'
-require 'spec/rake/spectask'
-
-desc 'Default: run specs.'
-task :default => :spec
-
-desc 'Run the specs'
-Spec::Rake::SpecTask.new(:spec) do |t|
-  t.spec_opts = ['--colour --format progress --loadby mtime --reverse']
-  t.spec_files = FileList['spec/**/*_spec.rb']
-end