README.markdown in deface-1.0.0.rc1 vs README.markdown in deface-1.0.0.rc2

- old
+ new

@@ -1,8 +1,8 @@ <p style="float:right;"> - <a href="http://travis-ci.org/#!/railsdog/deface"> - <img src="http://travis-ci.org/railsdog/deface.png"> + <a href="http://secure.travis-ci.org/spree/deface"> + <img src="https://secure.travis-ci.org/spree/deface.png?branch=master"> </a> </p> Deface ====== @@ -183,24 +183,24 @@ You can redefine an existing override by simply declaring a new override with the same <tt>:virtual_path</tt> and <tt>:name</tt> that was originally used. You do not need to resupply all the values originally used, just the ones you want to change: ```ruby - Deface::Override.new(:virtual_path => 'posts/index', - :name => 'add_attrs_to_a_link', - :disabled => true) +Deface::Override.new(:virtual_path => 'posts/index', + :name => 'add_attrs_to_a_link', + :disabled => true) ``` ### Namespacing If you want to avoid inadvertently redefining overrides in other engines, you can use the `namespaced` option to have an override automatically be namespaced to the engine in which it was defined: ```ruby - Deface::Override.new(:virtual_path => 'posts/index', - :name => 'add_link', - :namespaced => true) +Deface::Override.new(:virtual_path => 'posts/index', + :name => 'add_link', + :namespaced => true) ``` So for example if the above override was defined in `MyEngine` it would be automatically named `my_engine_add_link`. This can also be activated globally for all DSL overrides in your app's `application.rb` file: @@ -325,10 +325,12 @@ bundle exec rake deface:precompile It's important to disable Deface once precompiling is used to prevent overrides getting applied twice. To disable add the following line to your application's `production.rb` file: - config.deface.enabled = false +```ruby +config.deface.enabled = false +``` NOTE: You can also use precompiling in development mode. Demo & Testing