CMPE/SE 131 Software Engineering February 7 Class Meeting

Slides:



Advertisements
Similar presentations
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 15 Introduction to Rails.
Advertisements

Presenter: James Huang Date: Sept. 29,  HTTP and WWW  Bottle Web Framework  Request Routing  Sending Static Files  Handling HTML  HTTP Errors.
The Librarian Web Page Carol Wolf CS396X. Create new controller  To create a new controller that can manage more than just books, type ruby script/generate.
XML and Ruby on Rails Jennifer Andrews LIS 531F April 25,2007.
B.Sc. Multimedia ComputingMedia Technologies Database Technologies.
Creating a wiki blog. Run apps that come with instant rails distribution select I /rails applications/open ruby console window Cd to cookbook or typo.
Computer Science 101 Web Access to Databases Overview of Web Access to Databases.
Ruby on Rails Creating a Rails Application Carol E Wolf CS396X.
Christopher M. Pascucci Basic Structural Concepts of.NET Browser – Server Interaction.
Ruby on Rails. What is Ruby on Rails? Ruby on Rails is an open source full-stack web framework. It is an alternative to PHP/MySQL. It can render templates,
MVC in Trax.
Ruby on Rails CSCI 6314 David Gaspar Jennifer Garcia Avila.
Authentication/Authorization INFO 2310: Topics in Web Design and Programming.
1 Dr Alexiei Dingli Web Science Stream Models, Views and Controllers.
Server-side Scripting Powering the webs favourite services.
1 PHP and MySQL. 2 Topics  Querying Data with PHP  User-Driven Querying  Writing Data with PHP and MySQL PHP and MySQL.
Internet Forms and Database Bob Kisel Amgraf, Inc.
1 Dr Alexiei Dingli Web Science Stream Advanced ROR.
Lecture 19 Web Application Frameworks Boriana Koleva Room: C54
1 Dr Alexiei Dingli Web Science Stream Introducing Rails.
Ruby on Rails Your first app. Rails files app/ Contains the controllers, models, views and assets for your application. You’ll focus on this folder for.
ASP.NET Programming with C# and SQL Server First Edition Chapter 3 Using Functions, Methods, and Control Structures.
Introduction to Entity Framework Part 2 CRUD Scaffolding Tom Perkins NTPCUG.
School of Computing and Information Systems CS 371 Web Application Programming PHP – Forms, Cookies, Sessions and Database.
Lecture 11 Rails Topics SaaSSaaS Readings: SaaS book Ch February CSCE 740 Software Engineering.
Ruby on Rails CSE 190M, Spring 2009 Week 6. Overview How to use a database Demo creating a blog application on Rails Explain how the application works.
Associations INFO 2310: Topics in Web Design and Programming.
1 Dr Alexiei Dingli Web Science Stream A ROR Blog.
Photo Gallery INFO 2310: Topics in Web Design and Programming.
Rails & Ajax Module 5. Introduction to Rails Overview of Rails Rails is Ruby based “A development framework for Web-based applications” Rails uses the.
RUBY ON RAILS (RoR) Ishwor Khadka. Why Ruby on Rails?
Chapter 15 © 2013 by Pearson Overview of Rails - Rails is a development framework for Web-based applications - Based on MVC architecture for applications.
Create, Update and Delete Carol Wolf Computer Science.
8 Chapter Eight Server-side Scripts. 8 Chapter Objectives Create dynamic Web pages that retrieve and display database data using Active Server Pages Process.
ASP-2-1 SERVER AND CLIENT SIDE SCRITPING Colorado Technical University IT420 Tim Peterson.
Ruby on Rails Controller of MVC. Routes How we map URIs like /tweets/1 to calling the show method of the Controller.
Rails and routing INFO 2310: Topics in Web Design and Programming.
CS 160 and CMPE/SE 131 Software Engineering February 9 Class Meeting Department of Computer Science Department of Computer Engineering San José State University.
Introduction to information systems RUBY ON RAILS dr inż. Tomasz Pieciukiewicz.
CS 160 and CMPE/SE 131 Software Engineering February 11 Class Meeting Department of Computer Science Department of Computer Engineering San José State.
Ruby on Rails. Web Framework for Ruby Designed to make it easier to develop, deploy, and maintain web applications Design with Model-View-Controller –almost.
Generating XML Data from a Database Eugenia Fernandez IUPUI.
CMPE/SE 131 Software Engineering September 6 Class Meeting Department of Computer Engineering San José State University Fall 2016 Instructor: Ron Mak
National College of Science & Information Technology.
CMPE/SE 131 Software Engineering September 1 Class Meeting Department of Computer Engineering San José State University Fall 2016 Instructor: Ron Mak
Jim Fawcett CSE686 – Internet Programming Spring 2014
API (Application Program Interface)
Jim Fawcett CSE686 – Internet Programming Spring 2012
MVC Architecture, Symfony Framework for PHP Web Apps
REST: Web Services Abel Sanchez.
Play Framework: Introduction
Chapter 19 PHP Part III Credits: Parts of the slides are based on slides created by textbook authors, P.J. Deitel and H. M. Deitel by Prentice Hall ©
CMPE 280 Web UI Design and Development October 26 Class Meeting
CMPE 280 Web UI Design and Development October 24 Class Meeting
PHP / MySQL Introduction
Testing REST IPA using POSTMAN
ISC440: Web Programming 2 Server-side Scripting PHP 3
Web Browser server client 3-Tier Architecture Apache web server PHP
Controllers.
Lecture 1: Multi-tier Architecture Overview
Chapter 15 Introduction to Rails.
Introduction of Week 11 Return assignment 9-1 Collect assignment 10-1
REST APIs Maxwell Furman Department of MIS Fox School of Business
Technical Integration Guide
MVC Controllers.
MVC Controllers.
MVC Controllers.
CMPE/SE 131 Software Engineering February 2 Class Meeting
CMPE/SE 131 Software Engineering February 9 Class Meeting
Presentation transcript:

CMPE/SE 131 Software Engineering February 7 Class Meeting Department of Computer Engineering San José State University Spring 2017 Instructor: Ron Mak www.cs.sjsu.edu/~mak

We Have Teams! Clippers M.E.G.A. CMPE NoName3 Derailed Ruby Pear Fitness Team 131 Foodies Team NVC Frontier The Best GPS The Bugsters Hyper Ruby The Warriers

New Document Ruby on Rails Quick Start Guide https://goo.gl/uRdNhF

Full Stack Framework Includes everything you need to build a web application that: accepts user input queries databases responds with dynamically generated web pages

Three Types of MVC Objects Model objects Maintain the data and knowledge of your application. View objects Display the model to the user. The presentation layer. Controller objects Manage the application flow. Handle user interactions.

Update the Database Make changes to the record variable, and then call the save method. The save method returns true upon success. irb(main):020:0> post = Post.find 4 Post Load (0.1ms) SELECT "posts".* FROM "posts" WHERE "posts"."id" = ? LIMIT 1 [["id", 4]] => #<Post id: 4, title: "Third post!", body: "This is my third post.", created_at: "2016-02-04 08:47:56", updated_at: "2016-02-04 08:47:56"> irb(main):021:0> post.body = "My 3rd post." => "My 3rd post." irb(main):022:0> post.save (0.1ms) begin transaction SQL (18.5ms) UPDATE "posts" SET "body" = ?, "updated_at" = ? WHERE "posts"."id" = ? [["body", "My 3rd post."], ["updated_at", "2016-02-04 09:22:53.133946"], ["id", 4]] (6.2ms) commit transaction => true

Update the Database, cont’d The update method does the save. Returns true upon success. irb(main):023:0> post = Post.find 5 Post Load (0.1ms) SELECT "posts".* FROM "posts" WHERE "posts"."id" = ? LIMIT 1 [["id", 5]] => #<Post id: 5, title: "Fourth post", body: "This is my fourth post.", created_at: "2016-02-04 08:52:05", updated_at: "2016-02-04 08:52:05"> irb(main):024:0> post.update body: "My 4th post" (0.1ms) begin transaction SQL (19.2ms) UPDATE "posts" SET "body" = ?, "updated_at" = ? WHERE "posts"."id" = ? [["body", "My 4th post"], ["updated_at", "2016-02-04 09:30:23.755547"], ["id", 5]] (2.8ms) commit transaction => true

Delete Records Method destroy deletes records. Returns the records that were deleted. irb(main):025:0> post = Post.find 2 Post Load (0.2ms) SELECT "posts".* FROM "posts" WHERE "posts"."id" = ? LIMIT 1 [["id", 2]] => #<Post id: 2, title: "Second post!", body: "This is my second post.", created_at: "2016-02-04 07:53:37", updated_at: "2016-02-04 07:53:37”> irb(main):026:0> post.destroy (0.1ms) begin transaction SQL (1.7ms) DELETE FROM "posts" WHERE "posts"."id" = ? [["id", 2]] (5.6ms) commit transaction => #<Post id: 2, title: "Second post!", body: "This is my second post.", created_at: "2016-02-04 07:53:37", updated_at: "2016-02-04 07:53:37">

Delete Records Method destroy_all deletes from a relation. Returns the records that were deleted. irb(main):027:0> Post.where(title: "Fourth post").destroy_all Post Load (1.6ms) SELECT "posts".* FROM "posts" WHERE "posts"."title" = ? [["title", "Fourth post"]] (0.1ms) begin transaction SQL (0.3ms) DELETE FROM "posts" WHERE "posts"."id" = ? [["id", 5]] (5.6ms) commit transaction => [#<Post id: 5, title: "Fourth post", body: "My 4th post", created_at: "2016-02-04 08:52:05", updated_at: "2016-02-04 09:30:23">]

Query Calculations Use methods count, minimum, and maximum. irb(main):006:0> Post.count (0.2ms) SELECT COUNT(*) FROM "posts" => 4 irb(main):007:0> Post.minimum :id (0.2ms) SELECT MIN("posts"."id") FROM "posts" => 1 irb(main):008:0> Post.maximum :id (0.2ms) SELECT MAX("posts"."id") FROM "posts"

Database Schema Stores the current state of your database. db/schema.rb ActiveRecord::Schema.define(version: 20160901224633) do create_table "posts", force: :cascade do |t| t.string "title" t.text "body" t.datetime "created_at", null: false t.datetime "updated_at", null: false end

Database Migrations Ruby scripts that create and modify your database tables. Example: Add a column to a table. Stored in directory db/migrate. Each script is time-stamped (GMT) so that Rails can keep track of which migrations have already been run. bin/rake db:migrate to run migrations.

Add a Column to a Table The posts table currently has columns (fields) title and body. Let’s add an author column: Follow the naming convention add_ColumnName_to_TableName bin/rails g migration add_author_to_posts author:string bin/rake db:migrate

Data Validation You want to validate data before it enters the database. For example, ensure that the post title is not blank. Edit app/models/post.rb class Post < ActiveRecord::Base validates :title, :presence => true end irb(main):003:0> post = Post.new #<Post id: nil, title: nil, body: nil, created_at: nil, updated_at: nil, author: nil> irb(main):004:0> post.valid? => false irb(main):005:0> post.errors.full_messages => ["Title can't be blank"]

Table Associations We will add a new comments table. Each post has many comments. One-to-many relationship between the posts table and the comments table. Each comment will have a reference to the post that it belongs to. Many comments can reference the same post. bin/rails g model Comment author:string body:text post:references bin/rake db:migrate

Table Associations, cont’d Edit app/models/post.rb again to add the association: See also app/models/comment.rb: Restart the rails console. class Post < ActiveRecord::Base validates :title, :presence => true has_many :comments end class Comment < ActiveRecord::Base belongs_to :post end

Table Associations, cont’d Create comments and associate them with posts: irb(main):004:0> post = Post.first Post Load (0.2ms) SELECT "posts".* FROM "posts" ORDER BY "posts"."id" ASC LIMIT 1 => #<Post id: 1, title: "First post!", body: "This is my first post.", created_at: "2016-02-04 23:48:11", updated_at: "2016-02-04 23:48:11", author: nil> irb(main):006:0> post.comments.create author: "Bob", body: "Bob's comment" ... => #<Comment id: 1, author: "Bob", body: "Bob's comment", post_id: 1, ... > irb(main):007:0> post.comments Comment Load (0.2ms) SELECT "comments".* FROM "comments" WHERE "comments"."post_id" = ? [["post_id", 1]] => #<ActiveRecord::Associations::CollectionProxy [#<Comment id: 1, author: "Bob", body: "Bob's comment", post_id: 1, ... ">]>

Table Associations, cont’d irb(main):009:0> comment = Comment.create author: "Cindy", body: "Cindy's comment" ... => #<Comment id: 2, author: "Cindy", body: "Cindy's comment", post_id: nil, created_at: "2016-02-09 07:58:08", ... > irb(main):023:0> post.comments<< comment => #<ActiveRecord::Associations::CollectionProxy [#<Comment id: 1, author: "Bob", body: "Bob's comment", post_id: 1, ..., #<Comment id: 2, author: "Cindy", body: "Cindy's comment", post_id: 1, ... >]> irb(main):024:0> post.comments

Controllers Controllers receive commands from the user. Alters the state of the model. Modifies the view.

REST Rails applications use REST by default. Representational State Transfer Software architecture for client-server applications. RESTful systems communicate over HTTP. HTTP verbs GET, POST, PATCH, DELETE REST deals with resources (models).

Routing Routes connect URLs to the application’s server code. The most common type is the resource route. Stored in config/routes.rb. Rails.application.routes.draw do resources :posts do resources :comments, only: :create end get 'login' => 'user_session#new' post 'login' => 'user_session#create' delete 'logout' => 'user_sessions#destroy' root 'posts#index' Nested resource: Comments are available only inside of posts. Custom routes Root route

Routing, cont’d Display the application’s routes: ~/ruby/code/blog: bin/rake routes Running via Spring preloader in process 1581 Prefix Verb URI Pattern Controller#Action post_comments POST /posts/:post_id/comments(.:format) comments#create posts GET /posts(.:format) posts#index POST /posts(.:format) posts#create new_post GET /posts/new(.:format) posts#new edit_post GET /posts/:id/edit(.:format) posts#edit post GET /posts/:id(.:format) posts#show PATCH /posts/:id(.:format) posts#update PUT /posts/:id(.:format) posts#update DELETE /posts/:id(.:format) posts#destroy login GET /login(.:format) user_session#new POST /login(.:format) user_session#create logout DELETE /logout(.:format) user_sessions#destroy root GET / posts#index

Controller Actions Rails convention: Have a controller for each resource. The scaffolding code includes some basic actions. See app/controllers/posts_controllers.rb

Controller Actions, cont’d class PostsController < ApplicationController before_action :set_post, only: [:show, :edit, :update, :destroy] def index @posts = Post.all end def show def new @post = Post.new def edit ... Call the set_post method before executing the show, edit, update, or destroy methods. Private actions such as set_post go here.

Controller Actions, cont’d Private methods: private # Use callbacks to share common setup #or constraints between actions. def set_post @post = Post.find(params[:id]) end # Never trust parameters from the scary internet, #only allow the white list through. def post_params params.require(:post).permit(:title, :body) The id parameter passed via a submitted client form. Allow users to edit only the title and body of a post.

Redirect vs. Render Every controller action either renders a view or redirects to another action. Default: An action renders a file that matches the action name. Example: The post controller’s show method looks for the file app/views/posts/show.html.erb .erb are embedded Ruby files, such as HTML with embedded Ruby code. Render a response for a different action: render action: "edit"

Embedded Ruby File (.erb) <p id="notice"><%= notice %></p> <p> <strong>Title:</strong> <%= @post.title %> </p> <strong>Body:</strong> <%= @post.body %> <%= link_to 'Edit', edit_post_path(@post) %> | <%= link_to 'Back', posts_path %>

Redirect Redirect the user’s browser to another page: redirect_to @post

Response Formats Scaffold-generated controllers can respond in different formats. HTML JSON (JavaScript Object Notation) XML PDF JSON Example: http://localhost:3000/posts.json

Flash Messages Error messages or notices. Example from the create method: redirect_to @post, notice: 'Post was successfully created.'

The Comments Controller Generate a new controller for comments: ~/ruby/code/blog: bin/rails generate controller comments Running via Spring preloader in process 1782 create app/controllers/comments_controller.rb invoke erb create app/views/comments invoke test_unit create test/controllers/comments_controller_test.rb invoke helper create app/helpers/comments_helper.rb invoke test_unit invoke assets invoke coffee create app/assets/javascripts/comments.coffee invoke scss create app/assets/stylesheets/comments.scss empty controller empty directory

The Comments Controller, cont’d class CommentsController < ApplicationController def create @post = Post.find(params[:post_id]) if @post.comments.create(comment_params) redirect_to @post, notice: 'Comment was successfully created.' else alert: 'Error creating comment' end private def comment_params params.require(:comment).permit(:author, :body)