zurb-rush 0.0.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (55) hide show
  1. data/.gitignore +17 -0
  2. data/Gemfile +4 -0
  3. data/LICENSE +22 -0
  4. data/README.md +146 -0
  5. data/Rakefile +2 -0
  6. data/lib/zurb-rush.rb +8 -0
  7. data/lib/zurb-rush/form_builder.rb +32 -0
  8. data/lib/zurb-rush/railtie.rb +7 -0
  9. data/lib/zurb-rush/version.rb +3 -0
  10. data/lib/zurb-rush/view_helpers.rb +75 -0
  11. data/test_app/.gitignore +17 -0
  12. data/test_app/Gemfile +17 -0
  13. data/test_app/README.rdoc +261 -0
  14. data/test_app/Rakefile +7 -0
  15. data/test_app/app/assets/images/rails.png +0 -0
  16. data/test_app/app/assets/javascripts/application.js +16 -0
  17. data/test_app/app/assets/stylesheets/application.scss +1 -0
  18. data/test_app/app/assets/stylesheets/foundation_and_overrides.scss +60 -0
  19. data/test_app/app/controllers/application_controller.rb +3 -0
  20. data/test_app/app/controllers/demo_controller.rb +5 -0
  21. data/test_app/app/helpers/application_helper.rb +2 -0
  22. data/test_app/app/helpers/demo_helper.rb +2 -0
  23. data/test_app/app/mailers/.gitkeep +0 -0
  24. data/test_app/app/models/.gitkeep +0 -0
  25. data/test_app/app/views/demo/index.html.haml +54 -0
  26. data/test_app/app/views/layouts/application.html.erb +29 -0
  27. data/test_app/config.ru +4 -0
  28. data/test_app/config/application.rb +68 -0
  29. data/test_app/config/boot.rb +6 -0
  30. data/test_app/config/environment.rb +5 -0
  31. data/test_app/config/environments/development.rb +31 -0
  32. data/test_app/config/environments/production.rb +64 -0
  33. data/test_app/config/environments/test.rb +35 -0
  34. data/test_app/config/initializers/backtrace_silencers.rb +7 -0
  35. data/test_app/config/initializers/inflections.rb +15 -0
  36. data/test_app/config/initializers/mime_types.rb +5 -0
  37. data/test_app/config/initializers/secret_token.rb +7 -0
  38. data/test_app/config/initializers/session_store.rb +8 -0
  39. data/test_app/config/initializers/wrap_parameters.rb +10 -0
  40. data/test_app/config/locales/en.yml +5 -0
  41. data/test_app/config/routes.rb +4 -0
  42. data/test_app/lib/assets/.gitkeep +0 -0
  43. data/test_app/lib/tasks/.gitkeep +0 -0
  44. data/test_app/log/.gitkeep +0 -0
  45. data/test_app/public/404.html +26 -0
  46. data/test_app/public/422.html +26 -0
  47. data/test_app/public/500.html +25 -0
  48. data/test_app/public/favicon.ico +0 -0
  49. data/test_app/public/robots.txt +5 -0
  50. data/test_app/script/rails +6 -0
  51. data/test_app/vendor/assets/javascripts/.gitkeep +0 -0
  52. data/test_app/vendor/assets/stylesheets/.gitkeep +0 -0
  53. data/test_app/vendor/plugins/.gitkeep +0 -0
  54. data/zurb-rush.gemspec +19 -0
  55. metadata +149 -0
@@ -0,0 +1,17 @@
1
+ *.gem
2
+ *.rbc
3
+ .bundle
4
+ .config
5
+ .yardoc
6
+ Gemfile.lock
7
+ InstalledFiles
8
+ _yardoc
9
+ coverage
10
+ doc/
11
+ lib/bundler/man
12
+ pkg
13
+ rdoc
14
+ spec/reports
15
+ test/tmp
16
+ test/version_tmp
17
+ tmp
data/Gemfile ADDED
@@ -0,0 +1,4 @@
1
+ source 'https://rubygems.org'
2
+
3
+ # Specify your gem's dependencies in zurb-rush.gemspec
4
+ gemspec
data/LICENSE ADDED
@@ -0,0 +1,22 @@
1
+ Copyright (c) 2012 Clinton R. Nixon
2
+
3
+ MIT License
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining
6
+ a copy of this software and associated documentation files (the
7
+ "Software"), to deal in the Software without restriction, including
8
+ without limitation the rights to use, copy, modify, merge, publish,
9
+ distribute, sublicense, and/or sell copies of the Software, and to
10
+ permit persons to whom the Software is furnished to do so, subject to
11
+ the following conditions:
12
+
13
+ The above copyright notice and this permission notice shall be
14
+ included in all copies or substantial portions of the Software.
15
+
16
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
17
+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
18
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
19
+ NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
20
+ LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
21
+ OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
22
+ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
@@ -0,0 +1,146 @@
1
+ zurb-rush
2
+ =========
3
+
4
+ Zurb Rush is a collection of helpers and a form builder for Zurb Foundation 3.
5
+
6
+ ## Installation
7
+
8
+ Add this line to your application's Gemfile:
9
+
10
+ gem 'zurb-rush'
11
+
12
+ And then execute:
13
+
14
+ $ bundle
15
+
16
+ Or install it yourself as:
17
+
18
+ $ gem install zurb-rush
19
+
20
+ ## Usage
21
+
22
+ ### The Grid
23
+
24
+ The Foundation grid is made up of rows and columns, which can be nested. You have two helpers for these with the obvious names `row` and `column`. These accept any number of arguments, which will be converted into class names on the row or column.
25
+
26
+ ```erb
27
+ <%= row do %>
28
+ <%= columns 4, :mobile => 1 do %>
29
+ I saw the best minds of my generation
30
+ <% end %>
31
+ <%= columns 8, :mobile => 3 do %>
32
+ destroyed by madness, starving hysterical naked
33
+ <% end %>
34
+ <% end %>
35
+ ```
36
+
37
+ ### Alert Boxes and Flash Messages
38
+
39
+ Rails flash messages can be easily shown using Foundation's alert boxes. Foundation's alert boxes use a different naming scheme than the standard flash messages, so they are mapped, like so:
40
+
41
+ * Rails' `notice` -> Foundation's `success`
42
+ * Rails' `alert` -> Foundation's `alert`
43
+ * Rails' `info` -> Foundation's standard alert
44
+
45
+ This is specifically because `redirect_to` allows you to pass a flash message with the `:notice` and `:alert` keys. `info` has been mapped so you can use the standard alert box, since `alert` has been taken.
46
+
47
+ To display all your flash messages using Foundation's alerts, simply call `display_flash_messages`, like so:
48
+
49
+ ```erb
50
+
51
+ <header>
52
+ <%= display_flash_messages %>
53
+ ...
54
+ </header>
55
+ ```
56
+
57
+ If you want to show an alert box outside of the flash messages, you can simply call `alert_box`:
58
+
59
+ ```erb
60
+ <%= alert_box "This is a standard alert." %>
61
+ <%= alert_box "This is a success alert.", :success %>
62
+ <%= alert_box "This is an alert.", :alert %>
63
+ <%= alert_box "This is a secondary alert.", :secondary %>
64
+ ```
65
+
66
+ ### Labels
67
+
68
+ Labels are inline styles that can be used to call out certain sections or to display metadata. Do not confuse them with form labels. It is super-confusing.
69
+
70
+ ```erb
71
+ <%= label "Regular Label" %>
72
+ <%= label "Radius Label", :radius %>
73
+ <%= label "Round Label", :round %>
74
+ <%= label "Secondary Label", :secondary %>
75
+ <%= label "Alert Label with a Radius", :alert, :radius %>
76
+ <%= label "Rounded Success Label", :success, :round %>
77
+ ```
78
+
79
+
80
+ ### The Form Builder
81
+
82
+ To start using the form builder, use the helper `foundation_form_for`.
83
+
84
+ ```erb
85
+ <%= foundation_form_for @user do |f| %>
86
+ <%= f.input :username %>
87
+ <%= f.input :password %>
88
+ <%= f.button :submit %>
89
+ <% end %>
90
+ ```
91
+
92
+ `input` can take many options, as seen below:
93
+
94
+ ```erb
95
+ <%= foundation_form_for @user do |f| %>
96
+ <%= f.input :username, :label => "Your name" %>
97
+ <%= f.input :address, :field => {:columns => 8} %>
98
+ <%= f.input :email, :as => :email, :placeholder => "you@example.com" %>
99
+ <%= f.button :submit %>
100
+ <% end %>
101
+ ```
102
+
103
+ You can even use inline inputs:
104
+
105
+ ```erb
106
+ <%= foundation_form_for @user do |f| %>
107
+ <%= f.input :username, :inline => true,
108
+ :label => {:columns => 2, :mobile_columns => 1},
109
+ :field => {:columns => 10, :mobile_columns => 3} %>
110
+ <% end %>
111
+ ```
112
+
113
+ If you want to use Foundation forms, but need to separate the label and field, you can use the normal Rails form builder's methods, `label` and `text_field` (or `password_field` or others.) We also provide a `field` method that uses the same intelligent guessing as `input` so you don't have to do all the work.
114
+
115
+ ```erb
116
+ <%= foundation_form_for @user do |f| %>
117
+ <%= f.label :twitter %>
118
+ <%= row do %>
119
+ <%= columns 4 do %>
120
+ <%= row :class => 'collapsed' do %>
121
+ <%= columns 2, :mobile => 1 do %>
122
+ <span class="prefix">@</span>
123
+ <% end %>
124
+ <%= column 10, :mobile => 3 do %>
125
+ <%= f.field :twitter %>
126
+ <% end %>
127
+ <% end %>
128
+ <% end %>
129
+ <% end %>
130
+ <% end %>
131
+ ```
132
+
133
+ ### TODO
134
+
135
+ * :field options on forms.
136
+ * Inline inputs.
137
+ * Form error states.
138
+
139
+
140
+ ## Contributing
141
+
142
+ 1. Fork it
143
+ 2. Create your feature branch (`git checkout -b my-new-feature`)
144
+ 3. Commit your changes (`git commit -am 'Added some feature'`)
145
+ 4. Push to the branch (`git push origin my-new-feature`)
146
+ 5. Create new Pull Request
@@ -0,0 +1,2 @@
1
+ #!/usr/bin/env rake
2
+ require "bundler/gem_tasks"
@@ -0,0 +1,8 @@
1
+ require "action_view"
2
+ require "zurb-rush/version"
3
+ require "zurb-rush/view_helpers"
4
+ require "zurb-rush/railtie" if defined?(Rails)
5
+
6
+ module ZurbRush
7
+ # Your code goes here...
8
+ end
@@ -0,0 +1,32 @@
1
+ module ZurbRush
2
+ class FormBuilder < ActionView::Helpers::FormBuilder
3
+ FIELD_NAME_MATCHERS = {
4
+ /password/ => :password,
5
+ /search/ => :search,
6
+ /email/ => :email,
7
+ /phone/ => :phone,
8
+ /fax/ => :phone,
9
+ /url/ => :url,
10
+ /time_zone/ => :time_zone
11
+ }
12
+
13
+ def input(field_name, options = {})
14
+ label_text = options.delete(:label)
15
+ label(field_name, label_text) + field(field_name, options)
16
+ end
17
+
18
+ def field(field_name, options = {})
19
+ field_name = field_name.to_s
20
+
21
+ field_type = options.delete(:as)
22
+ field_type ||= FIELD_NAME_MATCHERS.to_a.select { |matcher, type| matcher === field_name }.map { |_, type| type }.first
23
+ field_type ||= :text
24
+
25
+ send("#{field_type}_field", field_name, options)
26
+ end
27
+
28
+ def time_zone_field(field_name, options)
29
+ time_zone_select(field_name, options)
30
+ end
31
+ end
32
+ end
@@ -0,0 +1,7 @@
1
+ module ZurbRush
2
+ class Railtie < Rails::Railtie
3
+ ActiveSupport.on_load(:action_view) do
4
+ include ZurbRush::ViewHelpers
5
+ end
6
+ end
7
+ end
@@ -0,0 +1,3 @@
1
+ module ZurbRush
2
+ VERSION = "0.0.1"
3
+ end
@@ -0,0 +1,75 @@
1
+ require 'action_view/helpers'
2
+ require 'humanize'
3
+ require 'zurb-rush/form_builder'
4
+
5
+ module ZurbRush
6
+ module ViewHelpers
7
+ include ActionView::Helpers::TagHelper
8
+
9
+ ## The Grid
10
+
11
+ def row(options = {})
12
+ options[:class] = add_to_class(options[:class], 'row')
13
+
14
+ content_tag :div, options do
15
+ yield
16
+ end
17
+ end
18
+
19
+ def columns(columns, options = {})
20
+ classes = ['columns']
21
+
22
+ columns = columns.humanize if columns.respond_to?(:humanize)
23
+ classes << columns
24
+
25
+ if options[:mobile]
26
+ mobile_cols = options.delete(:mobile)
27
+ mobile_cols = mobile_cols.humanize if mobile_cols.respond_to?(:humanize)
28
+ classes << "mobile-#{mobile_cols}"
29
+ end
30
+
31
+ options[:class] = add_to_class(options[:class], *classes)
32
+
33
+ content_tag :div, options do
34
+ yield
35
+ end
36
+ end
37
+
38
+ ## Alert Boxes
39
+
40
+ def alert_box(content, *classes)
41
+ content_tag :div, :class => add_to_class("alert-box", *classes) do
42
+ raw(content + content_tag(:a, '&times;', {:href => '#', :class => 'close'}, false))
43
+ end
44
+ end
45
+
46
+ def display_flash_messages
47
+ flash.inject "" do |message, (key, value)|
48
+ # Change to match up to Rails' flash expectations.
49
+ key = "success" if key.to_s == "notice"
50
+ message += alert_box(value, key)
51
+ end.html_safe
52
+ end
53
+
54
+ ## Labels
55
+
56
+ def label_box(content, *classes)
57
+ content_tag :span, content, :class => add_to_class("label", *classes)
58
+ end
59
+
60
+ ## Forms
61
+
62
+ def foundation_form_for(record, options = {}, &proc)
63
+ defaults = {:builder => ZurbRush::FormBuilder}
64
+ form_for(record, defaults.merge(options), &proc)
65
+ end
66
+
67
+ private
68
+
69
+ def add_to_class(current_class, *classes_to_add)
70
+ existing_classes = current_class.to_s.split(/s+/)
71
+ classes = existing_classes + classes_to_add
72
+ classes.map(&:to_s).join(" ")
73
+ end
74
+ end
75
+ end
@@ -0,0 +1,17 @@
1
+ # See http://help.github.com/ignore-files/ for more about ignoring files.
2
+ #
3
+ # If you find yourself ignoring temporary files generated by your text editor
4
+ # or operating system, you probably want to add a global ignore instead:
5
+ # git config --global core.excludesfile ~/.gitignore_global
6
+
7
+ # Ignore bundler config
8
+ /.bundle
9
+
10
+ # Ignore the default SQLite database.
11
+ /db/*.sqlite3
12
+
13
+ # Ignore all logfiles and tempfiles.
14
+ /log/*.log
15
+ /tmp
16
+ bin/
17
+ vendor/ruby/
@@ -0,0 +1,17 @@
1
+ source 'https://rubygems.org'
2
+
3
+ gem 'rails', '3.2.8'
4
+ gem 'jquery-rails'
5
+ gem 'zurb-rush', :path => '../'
6
+ gem 'haml'
7
+ gem 'passenger'
8
+
9
+ # Gems used only for assets and not required
10
+ # in production environments by default.
11
+ group :assets do
12
+ gem 'sass-rails', '~> 3.2.3'
13
+ gem 'coffee-rails', '~> 3.2.1'
14
+ gem 'uglifier', '>= 1.0.3'
15
+ gem 'compass-rails', '~> 1.0.3'
16
+ gem 'zurb-foundation', '~> 3.0.1'
17
+ end
@@ -0,0 +1,261 @@
1
+ == Welcome to Rails
2
+
3
+ Rails is a web-application framework that includes everything needed to create
4
+ database-backed web applications according to the Model-View-Control pattern.
5
+
6
+ This pattern splits the view (also called the presentation) into "dumb"
7
+ templates that are primarily responsible for inserting pre-built data in between
8
+ HTML tags. The model contains the "smart" domain objects (such as Account,
9
+ Product, Person, Post) that holds all the business logic and knows how to
10
+ persist themselves to a database. The controller handles the incoming requests
11
+ (such as Save New Account, Update Product, Show Post) by manipulating the model
12
+ and directing data to the view.
13
+
14
+ In Rails, the model is handled by what's called an object-relational mapping
15
+ layer entitled Active Record. This layer allows you to present the data from
16
+ database rows as objects and embellish these data objects with business logic
17
+ methods. You can read more about Active Record in
18
+ link:files/vendor/rails/activerecord/README.html.
19
+
20
+ The controller and view are handled by the Action Pack, which handles both
21
+ layers by its two parts: Action View and Action Controller. These two layers
22
+ are bundled in a single package due to their heavy interdependence. This is
23
+ unlike the relationship between the Active Record and Action Pack that is much
24
+ more separate. Each of these packages can be used independently outside of
25
+ Rails. You can read more about Action Pack in
26
+ link:files/vendor/rails/actionpack/README.html.
27
+
28
+
29
+ == Getting Started
30
+
31
+ 1. At the command prompt, create a new Rails application:
32
+ <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
33
+
34
+ 2. Change directory to <tt>myapp</tt> and start the web server:
35
+ <tt>cd myapp; rails server</tt> (run with --help for options)
36
+
37
+ 3. Go to http://localhost:3000/ and you'll see:
38
+ "Welcome aboard: You're riding Ruby on Rails!"
39
+
40
+ 4. Follow the guidelines to start developing your application. You can find
41
+ the following resources handy:
42
+
43
+ * The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
44
+ * Ruby on Rails Tutorial Book: http://www.railstutorial.org/
45
+
46
+
47
+ == Debugging Rails
48
+
49
+ Sometimes your application goes wrong. Fortunately there are a lot of tools that
50
+ will help you debug it and get it back on the rails.
51
+
52
+ First area to check is the application log files. Have "tail -f" commands
53
+ running on the server.log and development.log. Rails will automatically display
54
+ debugging and runtime information to these files. Debugging info will also be
55
+ shown in the browser on requests from 127.0.0.1.
56
+
57
+ You can also log your own messages directly into the log file from your code
58
+ using the Ruby logger class from inside your controllers. Example:
59
+
60
+ class WeblogController < ActionController::Base
61
+ def destroy
62
+ @weblog = Weblog.find(params[:id])
63
+ @weblog.destroy
64
+ logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
65
+ end
66
+ end
67
+
68
+ The result will be a message in your log file along the lines of:
69
+
70
+ Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
71
+
72
+ More information on how to use the logger is at http://www.ruby-doc.org/core/
73
+
74
+ Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
75
+ several books available online as well:
76
+
77
+ * Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
78
+ * Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
79
+
80
+ These two books will bring you up to speed on the Ruby language and also on
81
+ programming in general.
82
+
83
+
84
+ == Debugger
85
+
86
+ Debugger support is available through the debugger command when you start your
87
+ Mongrel or WEBrick server with --debugger. This means that you can break out of
88
+ execution at any point in the code, investigate and change the model, and then,
89
+ resume execution! You need to install ruby-debug to run the server in debugging
90
+ mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
91
+
92
+ class WeblogController < ActionController::Base
93
+ def index
94
+ @posts = Post.all
95
+ debugger
96
+ end
97
+ end
98
+
99
+ So the controller will accept the action, run the first line, then present you
100
+ with a IRB prompt in the server window. Here you can do things like:
101
+
102
+ >> @posts.inspect
103
+ => "[#<Post:0x14a6be8
104
+ @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
105
+ #<Post:0x14a6620
106
+ @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
107
+ >> @posts.first.title = "hello from a debugger"
108
+ => "hello from a debugger"
109
+
110
+ ...and even better, you can examine how your runtime objects actually work:
111
+
112
+ >> f = @posts.first
113
+ => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
114
+ >> f.
115
+ Display all 152 possibilities? (y or n)
116
+
117
+ Finally, when you're ready to resume execution, you can enter "cont".
118
+
119
+
120
+ == Console
121
+
122
+ The console is a Ruby shell, which allows you to interact with your
123
+ application's domain model. Here you'll have all parts of the application
124
+ configured, just like it is when the application is running. You can inspect
125
+ domain models, change values, and save to the database. Starting the script
126
+ without arguments will launch it in the development environment.
127
+
128
+ To start the console, run <tt>rails console</tt> from the application
129
+ directory.
130
+
131
+ Options:
132
+
133
+ * Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
134
+ made to the database.
135
+ * Passing an environment name as an argument will load the corresponding
136
+ environment. Example: <tt>rails console production</tt>.
137
+
138
+ To reload your controllers and models after launching the console run
139
+ <tt>reload!</tt>
140
+
141
+ More information about irb can be found at:
142
+ link:http://www.rubycentral.org/pickaxe/irb.html
143
+
144
+
145
+ == dbconsole
146
+
147
+ You can go to the command line of your database directly through <tt>rails
148
+ dbconsole</tt>. You would be connected to the database with the credentials
149
+ defined in database.yml. Starting the script without arguments will connect you
150
+ to the development database. Passing an argument will connect you to a different
151
+ database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
152
+ PostgreSQL and SQLite 3.
153
+
154
+ == Description of Contents
155
+
156
+ The default directory structure of a generated Ruby on Rails application:
157
+
158
+ |-- app
159
+ | |-- assets
160
+ | |-- images
161
+ | |-- javascripts
162
+ | `-- stylesheets
163
+ | |-- controllers
164
+ | |-- helpers
165
+ | |-- mailers
166
+ | |-- models
167
+ | `-- views
168
+ | `-- layouts
169
+ |-- config
170
+ | |-- environments
171
+ | |-- initializers
172
+ | `-- locales
173
+ |-- db
174
+ |-- doc
175
+ |-- lib
176
+ | `-- tasks
177
+ |-- log
178
+ |-- public
179
+ |-- script
180
+ |-- test
181
+ | |-- fixtures
182
+ | |-- functional
183
+ | |-- integration
184
+ | |-- performance
185
+ | `-- unit
186
+ |-- tmp
187
+ | |-- cache
188
+ | |-- pids
189
+ | |-- sessions
190
+ | `-- sockets
191
+ `-- vendor
192
+ |-- assets
193
+ `-- stylesheets
194
+ `-- plugins
195
+
196
+ app
197
+ Holds all the code that's specific to this particular application.
198
+
199
+ app/assets
200
+ Contains subdirectories for images, stylesheets, and JavaScript files.
201
+
202
+ app/controllers
203
+ Holds controllers that should be named like weblogs_controller.rb for
204
+ automated URL mapping. All controllers should descend from
205
+ ApplicationController which itself descends from ActionController::Base.
206
+
207
+ app/models
208
+ Holds models that should be named like post.rb. Models descend from
209
+ ActiveRecord::Base by default.
210
+
211
+ app/views
212
+ Holds the template files for the view that should be named like
213
+ weblogs/index.html.erb for the WeblogsController#index action. All views use
214
+ eRuby syntax by default.
215
+
216
+ app/views/layouts
217
+ Holds the template files for layouts to be used with views. This models the
218
+ common header/footer method of wrapping views. In your views, define a layout
219
+ using the <tt>layout :default</tt> and create a file named default.html.erb.
220
+ Inside default.html.erb, call <% yield %> to render the view using this
221
+ layout.
222
+
223
+ app/helpers
224
+ Holds view helpers that should be named like weblogs_helper.rb. These are
225
+ generated for you automatically when using generators for controllers.
226
+ Helpers can be used to wrap functionality for your views into methods.
227
+
228
+ config
229
+ Configuration files for the Rails environment, the routing map, the database,
230
+ and other dependencies.
231
+
232
+ db
233
+ Contains the database schema in schema.rb. db/migrate contains all the
234
+ sequence of Migrations for your schema.
235
+
236
+ doc
237
+ This directory is where your application documentation will be stored when
238
+ generated using <tt>rake doc:app</tt>
239
+
240
+ lib
241
+ Application specific libraries. Basically, any kind of custom code that
242
+ doesn't belong under controllers, models, or helpers. This directory is in
243
+ the load path.
244
+
245
+ public
246
+ The directory available for the web server. Also contains the dispatchers and the
247
+ default HTML files. This should be set as the DOCUMENT_ROOT of your web
248
+ server.
249
+
250
+ script
251
+ Helper scripts for automation and generation.
252
+
253
+ test
254
+ Unit and functional tests along with fixtures. When using the rails generate
255
+ command, template test files will be generated for you and placed in this
256
+ directory.
257
+
258
+ vendor
259
+ External libraries that the application depends on. Also includes the plugins
260
+ subdirectory. If the app has frozen rails, those gems also go here, under
261
+ vendor/rails/. This directory is in the load path.