parlement 0.14 → 0.17

data/vendor/plugins/engines/CHANGELOG

@@ -1,241 +0,0 @@
-= 1.2.0 - MASSIVE INTERNAL REFACTORING
-
-
-* !!!Support for Rails < 1.2 has been dropped!!!; if you are using Rails =< 1.1.6, please use Engines 1.1.6, available from http://svn.rails-engines.org/engines/tags/rel_1.1.6
-
-* Engines are dead! Long live plugins! There is now no meaningful notion of an engine - all plugins can take advantage of the more powerful features that the engines plugin provides by including app directories, etc.
-
-* Init_engine.rb is no longer used; please use the plugin-standard init.rb instead.
-
-* Engines.start is no longer required; please use the config.plugins array provided by Rails instead
-
-* To get the most benefit from Engines, set config.plugins to ["engines", "*"] to load the engines plugin first, and then all other plugins in their normal order after.
-
-* Access all loaded plugins via the new Rails.plugins array, and by name using Rails.plugins[:plugin_name].
-
-* Access plugin metadata loaded automatically from about.yml: Rails.plugins[:name].about. Plugin#version is provided directly, for easy access.
-
-* Module.config is has been removed - use mattr_accessor instead, and initialize your default values via the init.rb mechanism.
-
-* Public asset helpers have been rewritten; instead of engine_stylesheet, now use stylesheet_link_tag :name, :plugin => "plugin_name"
-
-* Plugin migrations have been reworked to integrate into the main migration stream. Please run script/generate plugin_migration to create plugin migrations in your main application.
-
-* The fixture method for loading fixtures against any class has been removed; instead, engines will now provide a mechanism for loading fixtures from all plugins, by mirroring fixtures into a common location.
-
-* All references to engines have been removed; For example, any rake tasks which applied to engines now apply to all plugins. The default Rails rake tasks for plugins are overridden where necessary.
-
-* Layouts can now be shared via plugins - inspiration gratefully taken from PluginAWeek's plugin_routing :)
-
-* Actual routing from plugins is now possible, by including routes.rb in your plugin directory and using the from_plugin method in config/routes.rb (Ticket #182)
-
-* Controllers are no longer loaded twice if they're not present in the normal app/ directory (Ticket #177)
-
-* The preferred location for javascripts/stylesheets/etc is now 'assets' rather than 'public'
-
-* Ensure that plugins started before routing have their controllers appropriately added to config.controller_paths (Ticket #258)
-
-* Removed Engines.version - it's not longer relevant, now we're loading version information from about.yml files.
-
-* Added a huge amount of documentation to all new modules.
-
-* Added new warning message if installation of engines 1.2.x is attempted in a Rails 1.1.x application
-
-* Added details of the removal of the config method to UPGRADING
-
-* Removed the plugins:info rake task in favour of adding information to script/about via the Rails::Info module (Ticket #261)
-
-* Improved handling of testing and documentation tasks for plugins
-
-
-
-= 1.1.4
-
-* Fixed creation of multipart emails (Ticket #190)
-
-* Added a temporary fix to the code-mixing issue. In your engine's test/test_helper.rb, please add the following lines:
-
-   # Ensure that the code mixing and view loading from the application is disabled
-   Engines.disable_app_views_loading = true
-   Engines.disable_app_code_mixing = true
-
-  which will prevent code mixing for controllers and helpers, and loading views from the application. One thing to remember is to load any controllers/helpers using 'require_or_load' in your tests, to ensure that the engine behaviour is respected (Ticket #135)
-
-* Added tasks to easily test engines individually (Ticket #120)
-
-* Fixture extensions will now fail with an exception if the corresponding class cannot be loaded (Ticket #138)
-
-* Patch for new routing/controller loading in Rails 1.1.6. The routing code is now replaced with the contents of config.controller_paths, along with controller paths from any started engines (Ticket #196)
-
-* Rails' Configuration instance is now stored, and available from all engines and plugins.
-
-
-
-= 1.1.3
-
-* Fixed README to show 'models' rather than 'model' class (Ticket #167)
-* Fixed dependency loading to work with Rails 1.1.4 (Ticket #180)
-
-
-
-= 1.1.2
-
-* Added better fix to version checking (Ticket #130, jdell@gbdev.com).
-
-* Fixed generated init_engine.rb so that VERSION module doesn't cause probems (Ticket #131, japgolly@gmail.com)
-
-* Fixed error with Rails 1.0 when trying to ignore the engine_schema_info table (Ticket #132, snowblink@gmail.com)
-
-* Re-added old style rake tasks (Ticket #133)
-
-* No longer adding all subdirectories of <engine>/app or <engine>/lib, as this can cause issues when files are grouped in modules (Ticket #149, kasatani@gmail.com)
-
-* Fixed engine precidence ordering for Rails 1.1 (Ticket #146)
-
-* Added new Engines.each method to assist in processing the engines in the desired order (Ticket #146)
-
-* Fixed annoying error message at appears when starting the console in development mode (Ticket #134)
-
-* Engines is now super-careful about loading the correct version of Rails from vendor (Ticket #154)
-
-
-
-= 1.1.1
-
-* Fixed migration rake task failing when given a specific version (Ticket #115)
-
-* Added new rake task "test:engines" which will test engines (and other plugins) but ensure that the test database is cloned from development beforehand (Ticket #125)
-
-* Fixed issue where 'engine_schema_info' table was included in schema dumps (Ticket #87)
-
-* Fixed multi-part emails (Ticket #121)
-
-* Added an 'install.rb' file to new engines created by the bundled generator, which installs the engines plugin automatically if it doesn't already exist (Ticket #122)
-
-* Added a default VERSION module to generated engines (Ticket #123)
-
-* Refactored copying of engine's public files to a method of an Engine instance. You can now call Engines.get(:engine_name).copy_public_files (Ticket #108)
-
-* Changed engine generator templates from .rb files to .erb files (Ticket #106)
-
-* Fixed the test_helper.erb file to use the correct testing extensions and not load any schema - the schema will be cloned automatically via rake test:engines
-
-* Fixed problem when running with Rails 1.1.1 where version wasn't determined correctly (Ticket #129)
-
-* Fixed bug preventing engines from loading when both Rails 1.1.0 and 1.1.1 gems are installed and in use.
-
-* Updated version (d'oh!)
-
-
-
-= 1.1.0
-
-* Improved regexp matching for Rails 1.0 engines with peculiar paths
-
-* Engine instance objects can be accessed via Engines[:name], an alias for Engines.get(:name) (Ticket #99)
-
-* init_engine.rb is now processed as the final step in the Engine.start process, so it can access files within the lib directory, which is now in the $LOAD_PATH at that point. (Ticket #99)
-
-* Clarified MIT license (Ticket #98)
-
-* Updated Rake tasks to integrate smoothly with Rails 1.1 namespaces
-
-* Changed the version to "1.1.0 (svn)"
-
-* Added more information about using the plugin with Edge Rails to the README
-
-* moved extensions into lib/engines/ directory to enable use of Engines module in extension code.
-
-* Added conditional require_or_load method which attempts to detect the current Rails version. To use the Edge Rails version of the loading mechanism, add the line:
-
-*   Engines.config :edge, true
-
-* to your environment.rb file.
-
-* Merged changes from /branches/edge and /branches/rb_1.0 into /trunk
-
-* engine_schema_info now respects the prefix/suffixes set for ActiveRecord::Base (Ticket #67)
-
-* added ActiveRecord::Base.wrapped_table_name(name) method to assist in determining the correct table name
-
-
-
-= 1.0.6
-
-* Added ability to determine version information for engines: rake engine_info
-
-* Added a custom logger for the Engines module, to stop pollution of the Rails logs.
-
-* Added some more tests (in particular, see rails_engines/applications/engines_test).
-
-* Another attempt at solving Ticket #53 - controllers and helpers should now be loadable from modules, and if a full path (including RAILS_ROOT/ENGINES_ROOT) is given, it should be safely stripped from the require filename such that corresponding files can be located in any active engines. In other words, controller/helper overloading should now completely work, even if the controllers/helpers are in modules.
-
-* Added (finally) patch from Ticket #22 - ActionMailer helpers should now load
-
-* Removed support for Engines.start :engine, :engine_name => 'whatever'. It was pointless.
-
-* Fixed engine name referencing; engine_stylesheet/engine_javascript can now happily use shorthand engine names (i.e. :test == :test_engine) (Ticket #45)
-
-* Fixed minor documentation error ('Engine.start' ==> 'Engines.start') (Ticket #57)
-
-* Fixed double inclusion of RAILS_ROOT in engine_migrate rake task (Ticket #61)
-
-* Added ability to force config values even if given as a hash (Ticket #62)
-
-
-
-= 1.0.5
-
-* Fixed bug stopping fixtures from loading with PostgreSQL
-
-
-
-= 1.0.4
-
-* Another attempt at loading controllers within modules (Ticket #56)
-
-
-
-= 1.0.3
-
-* Fixed serious dependency bug stopping controllers being loaded (Ticket #56)
-
-
-
-= 1.0.2
-
-* Fixed bug with overloading controllers in modules from /app directory
-
-* Fixed exception thrown when public files couldn't be created; exception is now logged (Ticket #52)
-
-* Fixed problem with generated test_helper.rb file via File.expand_path (Ticket #50)
-
-
-
-= 1.0.1
-
-* Added engine generator for creation of new engines
-
-* Fixed 'Engine' typo in README
-
-* Fixed bug in fixtures extensions
-
-* Fixed /lib path management bug
-
-* Added method to determine public directory location from Engine object
-
-* Fixed bug in the error message in get_engine_dir()
-
-* Added proper component loading
-
-* Added preliminary tests for the config() methods module
-
-
-
-= pre-v170
-
-* Fixed copyright notices to point to DHH, rather than me.
-
-* Moved extension require statements into lib/engines.rb, so the will be loaded if another module/file calls require 'engines
-
-* Added a CHANGELOG file (this file)

data/vendor/plugins/engines/MIT-LICENSE

@@ -1,21 +0,0 @@
-Copyright (c) 2007 James Adam
-
-The MIT License
-
-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/engines/README

@@ -1,64 +0,0 @@
-The engines plugin enhances Rails' own plugin framework, making it simple to share controllers, helpers, models, public assets, routes and migrations in plugins.
-
-For more information, see http://rails-engines.org
-
-= Using the plugin
-
-With engines 1.2, no extra configuration in environment.rb is required. Having the plugin installed will automatically enable sharing of code within <tt>plugin/app/</tt> directories. Developers should be aware that the <tt>config.plugins</tt> parameter can be used to control plugin load order, if this is important for your application.
-
-=== config.plugins
-
-With Rails 1.2, the <tt>config.plugins</tt> list can be used to specify the order in which plugins are loaded. It's recommended (although not required) that you load the engines plugin first, and any other plugins later. The engines plugin enhances Rails' processing of <tt>config.plugins</tt> for occasions where you only care about the order of a small selection of your application's plugins. For instance, if you want to load +engines+ first, and anything else afterwards, then
-
-  config.plugins = ["engines", "*"]
-  
-will ensure that engines is loaded first, and everything else (in whatever order Rails chooses) afterwards.
-
-== Better plugins
-
-In addition to the regular set of plugin-supported files (lib, init.rb, tasks, generators, tests), plugins can carry the following when the engines plugin is also installed.
-
-
-=== Controllers, Helpers, and Views
-
-Include these files in an <tt>app</tt> directory just like you would in a normal Rails application. If you need to override a method, view or partial, create the corresponding file in your main <tt>app</tt> directory and it will be used instead.
-
-* Controllers & Helpers: See Engines::RailsExtensions::Dependencies for more information.
-* Views: See Engines::RailsExtensions::Templates for more information.
-
-=== Models
-
-Model code can similarly be placed in an <tt>app/models/</tt> directory. Unfortunately, it's not possible to automatically override methods within a model; if your application needs to change the way a model behaves, consider creating a subclass, or replacing the model entirely within your application's <tt>app/models/</tt> directory. See Engines::RailsExtensions::Dependencies for more information.
-
-IMPORTANT NOTE: when you load code from within plugins, it is typically not handled well by Rails in terms of unloading and reloading changes. Look here for more information - http://rails-engines.org/development/common-issues-when-overloading-code-from-plugins/
-
-=== Routes
-
-Include your route declarations in a <tt>routes.rb</tt> file at the root of your plugins, e.g.:
-
-  connect "/my/url", :controller => "some_controller"
-  my_named_route "do_stuff", :controller => "blah", :action => "stuff"
-  # etc.
-  
-You can then load these files into your application by declaring their inclusion in the application's <tt>config/routes.rb</tt>:
-
-  map.from_plugin :plugin_name
-
-See Engines::RailsExtensions::Routing for more information.
-  
-=== Migrations
-
-Migrations record the changes in your database as your application evolves. With engines 1.2, migrations from plugins can also join in this evolution as first-class entities. To add migrations to a plugin, include a <tt>db/migrate/</tt> folder and add migrations there as normal. These migrations can then be integrated into the main flow of database evolution by running the plugin_migration generator:
-
-  script/generate plugin_migration
-  
-This will produce a migration in your application. Running this migration (via <tt>rake db:migrate</tt>, as normal) will migrate the database according to the latest migrations in each plugin. See Engines::RailsExtensions::Migrations for more information.
-
-
-=== More powerful Rake tasks
-
-The engines plugin enhances and adds to the suite of default rake tasks for working with plugins. The <tt>doc:plugins</tt> task now includes controllers, helpers and models under <tt>app</tt>, and anything other code found under the plugin's <tt>code_paths</tt> attribute. New testing tasks have been added to run unit, functional and integration tests from plugins, whilst making it easier to load fixtures from plugins. See Engines::Testing for more details about testing, and run
-
-  rake -T
-  
-to see the set of rake tasks available.

data/vendor/plugins/engines/Rakefile

@@ -1,32 +0,0 @@
-require 'rake'
-require 'rake/rdoctask'
-require 'tmpdir'
-
-task :default => :doc
-
-desc 'Generate documentation for the engines plugin.'
-Rake::RDocTask.new(:doc) do |doc|
-  doc.rdoc_dir = 'doc'
-  doc.title    = 'Engines'
-  doc.main     = "README"
-  doc.rdoc_files.include("README", "UPGRADING", "CHANGELOG", "MIT-LICENSE")
-  doc.rdoc_files.include('lib/**/*.rb')
-  doc.options << '--line-numbers' << '--inline-source'
-end
-
-desc 'Run the engine plugin tests within their test harness'
-task :cruise do
-  # checkout the project into a temporary directory
-  version = "rails_1.2"
-  test_dir = "#{Dir.tmpdir}/engines_plugin_#{version}_test"
-  puts "Checking out test harness for #{version} into #{test_dir}"
-  `svn co http://svn.rails-engines.org/test/engines/#{version} #{test_dir}`
-
-  # run all the tests in this project
-  Dir.chdir(test_dir)
-  load 'Rakefile'
-  puts "Running all tests in test harness"
-  ['db:migrate', 'test', 'test:plugins'].each do |t|
-    Rake::Task[t].invoke
-  end  
-end

data/vendor/plugins/engines/UPGRADING

@@ -1,93 +0,0 @@
-= Upgrading from Engines 1.1.x to Engines 1.2.x
-
-
-The 1.2 release of the engines plugin represents a significant rewrite of the internals. Now less intrusive into the core frameworks, it's even simpler for plugin developers to make more flexible plugins than Rails typically allows.
-
-However, as a consequence of change, you may need to make some adjustments to your application to get the most benefit. These are outlined below:
-
-
-== In your application
-
-The following changes will affect code in applications which use the engines plugin
-
-=== Change the engine_schema table to plugin_schema
-
-Because the engines plugin now works universally for any Rails plugin, the table used to store migration information has been renamed appropriately. We can also play nicely with other plugin_migration implementations by supporting this convention.
-
-
-=== Rename RAILS_ROOT/public/engine_files to RAILS_ROOT/public/plugin_assets
-
-Similarly, any plugin can now share stylesheets, images and so on via an assets folder, so the destination within the main public directory has been renamed to reflect this. You can simply delete the RAILS_ROOT/public/engine_files directory; the new one will be generated the next time your application starts.
-
-
-=== The engine_image, engine_stylesheet and engine_javascript helpers have been replaced with enhanced versions of the normal Rails asset helpers
-
-Now, it's simple to include an image from any plugin, by adding a plugin key to the helper's options hash:
-
-  image_tag "image.png", :plugin => "my_plugin"
-
-A similar convention exists for stylesheets and javascript files. Additionally, the old behaviour of automatically including assets which match the "engine"'s name has been dropped - only the files you explicitly request are included.
-
-
-=== Engines.start is replaced with config.plugins
-
-Rails' native configuration object now includes an array for specifying which plugins are loaded, and in what order. The engines plugin enhances this feature with a "*" wildcard, so that you can load any order-sensitive plugins, and then the rest in any order.
-
-  config.plugins = ["engines", "some_plugin", "another_plugin", "*"]
-  
-It's worth noting that the engines plugin no longer needs to be specifically loaded first, so most people can happily ignore the config.plugins array without any problems.
-
-
-=== The "config" method for "engine"-style configuration is no longer loaded by default. 
-
-See below.
-  
-  
-=== Any "engines" type rake tasks are now "plugin" tasks.
-
-The following rake tasks are now provided by the engines plugin for operating on your application's plugins (whenever a task can operate on a single plugin, this can be controlled by specifying PLUGIN=<name> on the commandline):
-  
-  db:fixtures:plugins:load  # load fixtures from plugins. 
-  
-  test:plugins:units        # Run tests from within <plugins>/test/units
-  test:plugins:functional   # Run tests from within <plugins>/test/functional
-  test:plugins:integration  # Run tests from within <plugins>/test/integration
-  test:plugins              # Run all tests from within <plugins>/test/*
-
-  doc:plugins               # Run full rdoc against all source files within all plugins
-  doc:plugins:<plugin>      # Run full rdoc against all source files within the given plugin
-
-
-
-== In your "engine"-style plugins
-
-If you have developed or are using plugins that leverage engines enhancements, you need to be aware of the following changes in engines 1.2.
-
-=== init_engine.rb is no longer required
-
-Please now create init.rb files, just as you'd find in "normal" plugins. Remember - there's no such thing as "an engine" anymore.
-
-
-=== The "fixture" method for loading tests from arbitrary files
-
-Supporting this was just too difficult, and it seems like the combination of Rails' own lack of enhancements regarding this feature, along with the mind-shift against static fixtures, meant that it simply was too much work to continue to support.
-
-The only reason this mechanism originally existed was to support plugins which couldn't predict the names of the tables that models might be stored in. This is now a discouraged behaviour.
-
-
-=== Engines.current.version has changed its behaviour slightly.
-
-The engines plugin used to provide a simple way to store version information about plugins. This has now been superceded by including that information in an about.yml file, which any plugin can use.
-
-
-=== The "config" method is not included, by default.
-
-Where previously developers could use the "config" method to define configuration, this is now deprecated in favour of using mattr_accessor directly in the Module. However, if you still *need* to use the config method, it is included but must be explicitly required, probably near the top of environment.rb:
-  
-  require File.join(RAILS_ROOT, "vendor", "plugins", "engines",
-                    "lib", "engines", "deprecated_config_support")
-
-
-=== Public assets should now be stored in a subdirectory of your plugin called "assets", rather than "public".
-
-This clarifies the nature of this directory; it is not made public itself, but rather is a container for files which should be made accessible from the web.