RubyGems - how_to - Versions diffs - 0.0.7 → 0.0.8 - Mend

how_to 0.0.7 → 0.0.8

Files changed (10) hide show

data/README.rdoc +4 -0
data/app/controllers/how_to/application_controller.rb +8 -0
data/app/controllers/how_to/faq_controller.rb +0 -2
data/app/controllers/how_to/sections_controller.rb +0 -2
data/app/views/layouts/how_to/application.html.erb +2 -2
data/lib/generators/how_to/templates/how_to_config.rb +4 -0
data/lib/how_to/config.rb +2 -0
data/lib/how_to/version.rb +1 -1
metadata +2 -4
data/test/dummy/README.rdoc +0 -261

data/README.rdoc CHANGED Viewed

@@ -3,7 +3,11 @@
 Rails engine that makes managing faq/manual easy and simple. Multilingual CMS for managing faq, question/answer, manual etc.
+{Live Demo}[http://how-to-demo.herokuapp.com]
+{Live demo source code}[https://github.com/railscash/how_to_demo]
 ===Usage
 ======Include the gem in your Gemfile and bundle to install the gem.

data/app/controllers/how_to/application_controller.rb CHANGED Viewed

@@ -1,5 +1,6 @@
 module HowTo
   class ApplicationController < ::ApplicationController
+    #layout :how_to_layout
     helper_method :can_manage_how_to?
     def can_manage_how_to?
@@ -14,5 +15,12 @@ module HowTo
       self.send(HowTo.config.authorization_method_to_view.to_sym) rescue true
     end
+    def how_to_layout
+      if template_exists?(HowTo.config.layout_name, "layouts/how_tos")
+        "how_to/#{HowTo.config.layout_name}"
+      else
+        nil
+      end
+    end
   end
 end

data/app/controllers/how_to/faq_controller.rb CHANGED Viewed

@@ -6,7 +6,5 @@ module HowTo
     def show
     end
   end
 end

data/app/controllers/how_to/sections_controller.rb CHANGED Viewed

@@ -63,7 +63,5 @@ module HowTo
         format.html { redirect_to sections_url }
       end
     end
   end
 end

data/app/views/layouts/how_to/application.html.erb CHANGED Viewed

@@ -2,8 +2,8 @@
 <html xmlns="http://www.w3.org/1999/html">
 <head>
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
-  <title><%= content_for?(:title) ? yield(:title) : "App_Name" %></title>
-  <meta name="description" content="<%= content_for?(:description) ? yield(:description) : "App_Name" %>">
+  <title><%= content_for?(:title) ? yield(:title) : "App Name" %></title>
+  <meta name="description" content="<%= content_for?(:description) ? yield(:description) : "App desc" %>">
   <%= stylesheet_link_tag "how_to/application", :media => "all" %>
   <%= javascript_include_tag "how_to/application" %>
   <%= csrf_meta_tags %>

data/lib/generators/how_to/templates/how_to_config.rb CHANGED Viewed

@@ -4,6 +4,10 @@ HowTo.configure do |config|
   #You have to install mercury to your application
   #config.rich_text_enabled = false
+  # You can override the layout name
+  #
+  #config.layout_name = 'application'
   #in your application controller:
   # def authorize_to_manage_how_to
   #  redirect_to :somewhere_else unless <condition>

data/lib/how_to/config.rb CHANGED Viewed

@@ -14,6 +14,7 @@ module HowTo
   class Configuration #:nodoc:
     include ActiveSupport::Configurable
     config_accessor :rich_text_enabled
+    config_accessor :layout_name
     config_accessor :authorization_method_to_manage
     config_accessor :authorization_method_to_view
     config_accessor :permitted_to_manage_how_to
@@ -21,6 +22,7 @@ module HowTo
   configure do |config|
     config.rich_text_enabled = false
+    config.layout_name = 'application'
     config.authorization_method_to_manage = 'authorize_to_manage_how_to'
     config.authorization_method_to_view = nil
     config.permitted_to_manage_how_to = 'permitted_to_manage_how_to?'

data/lib/how_to/version.rb CHANGED Viewed

@@ -1,3 +1,3 @@
 module HowTo
-  VERSION = "0.0.7"
+  VERSION = "0.0.8"
 end

metadata CHANGED Viewed

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: how_to
 version: !ruby/object:Gem::Version
-  version: 0.0.7
+  version: 0.0.8
   prerelease:
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2013-09-06 00:00:00.000000000 Z
+date: 2014-03-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -203,7 +203,6 @@ files:
 - test/dummy/public/system/images/1/original/Screen_Shot_2013-05-06_at_6.29.38_PM.png
 - test/dummy/public/system/images/1/thumb/Screen_Shot_2013-05-06_at_6.29.38_PM.png
 - test/dummy/Rakefile
-- test/dummy/README.rdoc
 - test/dummy/script/rails
 - test/dummy/tmp/cache/assets/C19/4E0/sprockets%2F219d43b8396c33bb4240973157007f24
 - test/dummy/tmp/cache/assets/C19/D70/sprockets%2F95f2176b2b35403940711067337fbc45
@@ -587,7 +586,6 @@ test_files:
 - test/dummy/public/system/images/1/original/Screen_Shot_2013-05-06_at_6.29.38_PM.png
 - test/dummy/public/system/images/1/thumb/Screen_Shot_2013-05-06_at_6.29.38_PM.png
 - test/dummy/Rakefile
-- test/dummy/README.rdoc
 - test/dummy/script/rails
 - test/dummy/tmp/cache/assets/C19/4E0/sprockets%2F219d43b8396c33bb4240973157007f24
 - test/dummy/tmp/cache/assets/C19/D70/sprockets%2F95f2176b2b35403940711067337fbc45

data/test/dummy/README.rdoc DELETED Viewed

@@ -1,261 +0,0 @@
-== Welcome to Rails
-Rails is a web-application framework that includes everything needed to create
-database-backed web applications according to the Model-View-Control pattern.
-This pattern splits the view (also called the presentation) into "dumb"
-templates that are primarily responsible for inserting pre-built data in between
-HTML tags. The model contains the "smart" domain objects (such as Account,
-Product, Person, Post) that holds all the business logic and knows how to
-persist themselves to a database. The controller handles the incoming requests
-(such as Save New Account, Update Product, Show Post) by manipulating the model
-and directing data to the view.
-In Rails, the model is handled by what's called an object-relational mapping
-layer entitled Active Record. This layer allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
-link:files/vendor/rails/activerecord/README.html.
-The controller and view are handled by the Action Pack, which handles both
-layers by its two parts: Action View and Action Controller. These two layers
-are bundled in a single package due to their heavy interdependence. This is
-unlike the relationship between the Active Record and Action Pack that is much
-more separate. Each of these packages can be used independently outside of
-Rails. You can read more about Action Pack in
-link:files/vendor/rails/actionpack/README.html.
-== Getting Started
-1. At the command prompt, create a new Rails application:
-       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
-2. Change directory to <tt>myapp</tt> and start the web server:
-       <tt>cd myapp; rails server</tt> (run with --help for options)
-3. Go to http://localhost:3000/ and you'll see:
-       "Welcome aboard: You're riding Ruby on Rails!"
-4. Follow the guidelines to start developing your application. You can find
-the following resources handy:
-* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
-* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
-== Debugging Rails
-Sometimes your application goes wrong. Fortunately there are a lot of tools that
-will help you debug it and get it back on the rails.
-First area to check is the application log files. Have "tail -f" commands
-running on the server.log and development.log. Rails will automatically display
-debugging and runtime information to these files. Debugging info will also be
-shown in the browser on requests from 127.0.0.1.
-You can also log your own messages directly into the log file from your code
-using the Ruby logger class from inside your controllers. Example:
-  class WeblogController < ActionController::Base
-    def destroy
-      @weblog = Weblog.find(params[:id])
-      @weblog.destroy
-      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
-    end
-  end
-The result will be a message in your log file along the lines of:
-  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
-More information on how to use the logger is at http://www.ruby-doc.org/core/
-Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
-several books available online as well:
-* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
-* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
-These two books will bring you up to speed on the Ruby language and also on
-programming in general.
-== Debugger
-Debugger support is available through the debugger command when you start your
-Mongrel or WEBrick server with --debugger. This means that you can break out of
-execution at any point in the code, investigate and change the model, and then,
-resume execution! You need to install ruby-debug to run the server in debugging
-mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.all
-      debugger
-    end
-  end
-So the controller will accept the action, run the first line, then present you
-with a IRB prompt in the server window. Here you can do things like:
-  >> @posts.inspect
-  => "[#<Post:0x14a6be8
-          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
-       #<Post:0x14a6620
-          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
-  >> @posts.first.title = "hello from a debugger"
-  => "hello from a debugger"
-...and even better, you can examine how your runtime objects actually work:
-  >> f = @posts.first
-  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
-  >> f.
-  Display all 152 possibilities? (y or n)
-Finally, when you're ready to resume execution, you can enter "cont".
-== Console
-The console is a Ruby shell, which allows you to interact with your
-application's domain model. Here you'll have all parts of the application
-configured, just like it is when the application is running. You can inspect
-domain models, change values, and save to the database. Starting the script
-without arguments will launch it in the development environment.
-To start the console, run <tt>rails console</tt> from the application
-directory.
-Options:
-* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
-  made to the database.
-* Passing an environment name as an argument will load the corresponding
-  environment. Example: <tt>rails console production</tt>.
-To reload your controllers and models after launching the console run
-<tt>reload!</tt>
-More information about irb can be found at:
-link:http://www.rubycentral.org/pickaxe/irb.html
-== dbconsole
-You can go to the command line of your database directly through <tt>rails
-dbconsole</tt>. You would be connected to the database with the credentials
-defined in database.yml. Starting the script without arguments will connect you
-to the development database. Passing an argument will connect you to a different
-database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
-PostgreSQL and SQLite 3.
-== Description of Contents
-The default directory structure of a generated Ruby on Rails application:
-  |-- app
-  |   |-- assets
-  |   |   |-- images
-  |   |   |-- javascripts
-  |   |   `-- stylesheets
-  |   |-- controllers
-  |   |-- helpers
-  |   |-- mailers
-  |   |-- models
-  |   `-- views
-  |       `-- layouts
-  |-- config
-  |   |-- environments
-  |   |-- initializers
-  |   `-- locales
-  |-- db
-  |-- doc
-  |-- lib
-  |   |-- assets
-  |   `-- tasks
-  |-- log
-  |-- public
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   `-- cache
-  |       `-- assets
-  `-- vendor
-      |-- assets
-      |   |-- javascripts
-      |   `-- stylesheets
-      `-- plugins
-app
-  Holds all the code that's specific to this particular application.
-app/assets
-  Contains subdirectories for images, stylesheets, and JavaScript files.
-app/controllers
-  Holds controllers that should be named like weblogs_controller.rb for
-  automated URL mapping. All controllers should descend from
-  ApplicationController which itself descends from ActionController::Base.
-app/models
-  Holds models that should be named like post.rb. Models descend from
-  ActiveRecord::Base by default.
-app/views
-  Holds the template files for the view that should be named like
-  weblogs/index.html.erb for the WeblogsController#index action. All views use
-  eRuby syntax by default.
-app/views/layouts
-  Holds the template files for layouts to be used with views. This models the
-  common header/footer method of wrapping views. In your views, define a layout
-  using the <tt>layout :default</tt> and create a file named default.html.erb.
-  Inside default.html.erb, call <% yield %> to render the view using this
-  layout.
-app/helpers
-  Holds view helpers that should be named like weblogs_helper.rb. These are
-  generated for you automatically when using generators for controllers.
-  Helpers can be used to wrap functionality for your views into methods.
-config
-  Configuration files for the Rails environment, the routing map, the database,
-  and other dependencies.
-db
-  Contains the database schema in schema.rb. db/migrate contains all the
-  sequence of Migrations for your schema.
-doc
-  This directory is where your application documentation will be stored when
-  generated using <tt>rake doc:app</tt>
-lib
-  Application specific libraries. Basically, any kind of custom code that
-  doesn't belong under controllers, models, or helpers. This directory is in
-  the load path.
-public
-  The directory available for the web server. Also contains the dispatchers and the
-  default HTML files. This should be set as the DOCUMENT_ROOT of your web
-  server.
-script
-  Helper scripts for automation and generation.
-test
-  Unit and functional tests along with fixtures. When using the rails generate
-  command, template test files will be generated for you and placed in this
-  directory.
-vendor
-  External libraries that the application depends on. Also includes the plugins
-  subdirectory. If the app has frozen rails, those gems also go here, under
-  vendor/rails/. This directory is in the load path.