refactor the naming within plugin new generator

Having a method called `full?`, which checks on :full and :mountable
is very confusing. I renamed `full?` to `engine?` and created a `full?`
method that only checks the `:full` option
Use attr_accessor for Rails.{application,cache,logger}
Add periodical-style TOC and navigation to Kindle version of guides
add a notice about loading assets in production mode
Merge pull request #120 from tonytonyjan/patch

add a notice about loading assets in production mode
Correct bad English
Define a generator before referring to it
Introduce Bundler and Gemfiles in a NOTE
correct bad jquery syntax
adding example for f.file_input
adding example for f.file_input
complementary options guidelines for f.file_field and file_field_tag
API reader should look elsewhere for helper instructions
changing tense, since Rails 3.2 has been released
Added overview items to Guides Guidelines prologue
Fixed grammar in a lot of guide prologues.
Fix small grammatical error
Fix README
Rollback where.like and where.not_like

The real win with these chain methods is where.not, that takes care of
different scenarios in a graceful way, for instance when the given value
is nil.

    where("author.id != ?", author_to_ignore.id)
    where.not("author.id", author_to_ignore.id)

Both where.like and where.not_like compared to the SQL versions doesn't
seem to give us that much:

    Post.where("title LIKE 'ruby on%'")
    Post.where.like(title: 'ruby on%'")
    Post.where("title NOT LIKE 'ruby on%'")
    Post.where.not_like(title: 'ruby on%'")

Thus Rails is adding where.not, but not where.like/not_like and others.
Rename ActiveSupport::BasicObject to ActiveSupport::ProxyObject

AS::BasicObject is used for proxy classes. Let's give it a less concerning
name. Also, it avoids the confusion with Ruby's Basic Object.