CSC/ECE 517 Fall 2009/wiki1b 13 Resources For Rails: Difference between revisions
No edit summary |
No edit summary |
||
Line 35: | Line 35: | ||
Resource Type: Getting Started Tutorial | Resource Type: Getting Started Tutorial | ||
Examples Provided: The Rails cookbook application. | Examples Provided: The Rails cookbook application. | ||
Summary: This is a good starting point for someone new to Ruby and Rails. It starts assuming you don't have Ruby installed. At the end of the tutorial, a user should have a fully functioning Rails environment and | Summary: This is a good starting point for someone new to Ruby and Rails. It starts assuming you don't have Ruby installed. At the end of the tutorial, a user should have a fully functioning Rails environment and a sample application. The second part of the extends the cookbook example while describing more features of Rails. At the end of the tutorial there are Rails success stories and even more info about features of Rails such as caching, validation callbacks, and transactions. | ||
Rating: **** | Rating: **** | ||
Reason for Rating: | Reason for Rating: This is great starting point. The drawbacks are: 1 - tutorial assumes you are installing on Windows 2 - tutorial is not up to date with the latest Rails framework. | ||
</pre></code> | </pre></code> | ||
Link: http://oreilly.com/ruby/archive/rails.html | Link: http://oreilly.com/ruby/archive/rails.html |
Revision as of 15:00, 21 September 2009
About this Page
This page is a resource for more information regarding the Rails application framework. Consider it an index page for Rails resouces that also has definitions and extra information a user will find helpful before they go to the resource. Ruby programmers that want to get started with Rails are the target audience. We do not cover information regarding IDE's. We chose the following topics as they are relevant to the target audience:
- Tutorials
- Testing
- Debugging
- Platform Issues
Each section starts with an introduction to convey the coverage provided by that topic. Definitions are provided to familiarize the audience with terms before they investigate a resource. Since information is usually made more clear through examples, look for our summary boxes; this is where we evaluate the resource and examples. Summary boxes look like this:
Name of Resource:
Resource Type:
Examples Provided:
Summary:
Rating:
Reason for Rating:
Summary boxes give you information about what they might expect in the resource before they start. Ratings are out of 5 stars. 5 stars is the highest rating.
This page is not meant to be a source of completely new information regarding the Rails platform. The new and unique content is our intro, definitions, and summary box. This it is meant to be used as a starting point for someone interested in more resources for Rails. We hope you find the information helpful!
For feedback please contact handles: objectoriented or cybo on the NCSU Expertiza system.
Resources for Rails
Tutorials
Topic Introduction
Definitions
Summary Boxes
Name of Resource: Rolling with Ruby on Rails
Resource Type: Getting Started Tutorial
Examples Provided: The Rails cookbook application.
Summary: This is a good starting point for someone new to Ruby and Rails. It starts assuming you don't have Ruby installed. At the end of the tutorial, a user should have a fully functioning Rails environment and a sample application. The second part of the extends the cookbook example while describing more features of Rails. At the end of the tutorial there are Rails success stories and even more info about features of Rails such as caching, validation callbacks, and transactions.
Rating: ****
Reason for Rating: This is great starting point. The drawbacks are: 1 - tutorial assumes you are installing on Windows 2 - tutorial is not up to date with the latest Rails framework.
Link: http://oreilly.com/ruby/archive/rails.html http://oreilly.com/ruby/archive/rails2.html
Name of Resource:
Resource Type:
Examples Provided:
Summary:
Rating:
Reason for Rating:
Link: http://rails.homelinux.org/
Name of Resource:
Resource Type:
Examples Provided:
Summary:
Rating:
Reason for Rating:
Link: http://www.slash7.com/articles/2005/01/24/really-getting-started-in-rails
Name of Resource:
Resource Type:
Examples Provided:
Summary:
Rating:
Reason for Rating:
Link: http://www.ibm.com/developerworks/linux/library/l-rubyrails/
Name of Resource:
Resource Type:
Examples Provided:
Summary:
Rating:
Reason for Rating:
Link: http://onlamp.com/pub/a/onlamp/2005/06/09/rails_ajax.html
Name of Resource:
Resource Type:
Examples Provided:
Summary:
Rating:
Reason for Rating:
Link: http://jrhicks.net/Projects/rails/has_many_and_belongs_to_many.pdf
Name of Resource:
Resource Type:
Examples Provided:
Summary:
Rating:
Reason for Rating:
Link: http://www.erikveen.dds.nl/distributingrubyapplications/rails.html
Name of Resource:
Resource Type:
Examples Provided:
Summary:
Rating:
Reason for Rating:
Link: http://digitalmediaminute.com/howto/fc4rails/
Testing
Topic Introduction
This section provides links to pages which describe resources that can be used by Ruby on Rails to conduct testing. Some of them are tutorials and some are just information that you need to know. This page also provides some definitions used by the links. In most cases the text in those links is intuitive however if you don’t understand something you can refer to the definition section. This page was written and the links were provided under the assumption that the reader has intermediate knowledge of Ruby (after all rails is a framework for Ruby not the actual language).
Definitions
XP – extreme programming. Here is the Wikipedia definition. Basically it means that at least one pair of eyes should look at your code, say a fellow developer. (S)he might be able to find errors that you are not able to. Say you wrote a method and it doesn’t the way you wanted it to. Let you programmer friend take a look at it. Frequent testing is also a part of this methodology.
BDD – behavior driven development. Here is the Wikipedia definition. But in plain English it means that when you work on a project you define its behavior, not the technical details of its implementation. Say you work with a customer on a webcatalog. You shouldn’t bore him/her with the technical detail of how you are going to do it. Just say that catalog will probably have administrators who can edit it, users who can view it, a shopping cart so that the product could be checked out, login and logout pages etc. That will define what this webcatalog can do (its behavior).
TDD – test driven development. Here is the Wikipedia definition. In other words you write a test before you write your code. Say you know that you have to write a method named do_something. Before writing it you will write a test for it, test_do_something and only then do_something. This methodology helps you to 1) define what your method should do exactly, since before you wrote it you already have a test for it so in some sense you already know what you expect your method to do 2)verify if you defined your method the way you wanted, because if you didn’t then your test will most likely fail
ZenTest – a set of tools that are used for testing in Ruby on Rails. Also it is a name of the tools in the ZenTest tool package. It should be installed separately. To install use: gem install ZenTest (Windows) or sudo gem install ZenTest (Linux)
RoR – abbreviation for Ruby on Rails
rake – ruby make utility
Resources
http://www.scribd.com/doc/3499573/TestFirst-Programming-With-Ruby I think this a good tutorial on how to do testing. It uses Test::Unit, how to set it up a test, and run it. It also introduces you to ZenTest. I’d say you should go through this tutorial first.
http://guides.rubyonrails.org/testing.html This is a decent guide/tutorial on testing. It provides you with introduction on testing in RoR, how to test your models, function tests of the controllers, how to use rake for testing etc. It also contains links to other guides on other testing approaches.
http://ph7spot.com/articles/getting_started_with_autotest This is a sort of a tutorial on how to use autotest utility from the ZenTest gem. I say sort of since you should use this tutorial on a already written code.
http://zentest.rubyforge.org/ZenTest This page contains documentation on ZenTest package. There are no examples of any kind just very dry documentation. You should use this as a reference when you become experienced with testing.
Debuging
Outline:
Coverage: Describe the scope of this page.
For each section:
Intro - what this set of resources is for.
Definition - look through resources and create a list of definitions for each.
Examples - describe an example similar to what is in the resource.
Links - organize by subtopic and crossrefereance with definitions and examples.
Resources
General
http://en.wikipedia.org/wiki/Ruby_on_Rails
http://rubyonrails.org/documentation
http://www.planetrubyonrails.org/
http://weblog.rubyonrails.org/2009/9/4/xss-vulnerability-in-ruby-on-rails
http://www.techcrunch.com/2008/05/01/twitter-said-to-be-abandoning-ruby-on-rails/
Tutorials
http://oreilly.com/ruby/archive/rails.html
http://oreilly.com/ruby/archive/rails2.html
http://www.slash7.com/articles/2005/01/24/really-getting-started-in-rails
http://www.ibm.com/developerworks/linux/library/l-rubyrails/
http://onlamp.com/pub/a/onlamp/2005/06/09/rails_ajax.html
http://jrhicks.net/Projects/rails/has_many_and_belongs_to_many.pdf
http://www.erikveen.dds.nl/distributingrubyapplications/rails.html
http://digitalmediaminute.com/howto/fc4rails/
Testing
http://guides.rubyonrails.org/testing.html
http://weblogs.java.net/blog/bleonard/archive/2008/01/testing_rails_a.html
http://www.oreillynet.com/pub/a/ruby/2007/06/07/rails-testing-not-just-for-the-paranoid.html
Debugging