To Do:
- Set up a focus group (like a study group for peer learning) to work on the Ruby on Rails workshops via Interact tools as a class.
- What is meant by “convention over configuration” and how does it reduce coding?
- Further work on understanding MVC: a. See the wiki at http://wiki.rubyonrails.org/rails/pages/UnderstandingMVC b. Do the MVC tutorial at http://wiki.squeak.org/squeak/1767
- Got a spare hour or so? I recommend the UC Berkeley RAD lab’s Ruby on Rails Short course at http://youtube.com/watch?v=LADHwoN2LMM
- Read the Flash article using ActionScript by Colin Moock titled “The Model-View-Controller Design Pattern “at http://www.adobe.com/devnet/flash/articles/mv_controller.html
Answer:
1. I have made a focus group in CSU interact forum and the same focus group will also be posted in my blog - http://itc594josephc.blogspot.com/search/label/Focus%20Group
2. Convention over configuration means a developer only needs to specify unconventional aspects of the application. For example, if there is a class Sale in the model, the corresponding table in the database is called sales by default. It is only if one deviates from this convention, such as calling the table "products sold", that the developer needs to write code regarding these names. Generally, this leads to less code and less repetition. (Wikipedia, 2009)
Personally, after using ROR, most of the configuration for database access is done by ROR by default. The developer only needs to write codes mainly for the View layer and the Controller Layer when Model Layer handles database access through the configuration file database.yml.
3. http://wiki.rubyonrails.org/rails/pages/UnderstandingMVC
4. I have viewed the course in youtube - http://youtube.com/watch?v=LADHwoN2LMM
5. I have downloaded and already read the article in http://www.adobe.com/devnet/flash/articles/mv_controller.html
Reference:
1. Wikipedia (2009), "Ruby on Rails". Wikipedia The Free Encyclopedia, Retrieved from URL - http://en.wikipedia.org/wiki/Ruby_on_Rails
