Skip to main content

How Sinatra works

Sinatra is a ruby gem application that allow you to build web site quickly. The method it uses is named after http request method like (get, post or put).

It also uses a templating language like ERB. HTML and Ruby can be integrated inside these templating language pages.


1. The last line in the block is return to the browser:

get '/' do
    erb :layout
end

This will return the erb file to the browser.

2. <%= @value %>
This will print out the value of @value.


3. For the value of params ,as far as I know, can be added like this

a. index.html/?key=name
- this will create params[:key] = name

b.
get "/:name" ; end
index.html/michael
- this will create params[:name]  = "michael"

c.
inside a form

<input name="list_name" placeholder="List Name" type="text" value="">

- this will create params[:list_name] = value

4. Instance Var define in other block is inaccessible by other block
eg :
get '/' do
   @value = 1
end

get '/hello' do
   @value    #=> return nil.
end

But is accessible via a 'before' block
before do
   @value = 10
end

get '/' do
   @value   # returns 10
end


Labels:

Comments

Post a Comment

Popular posts from this blog

Problem Solving - Refactored

I am going to outline how I approach problem solving. The relative importance and the amount of effort/time required for each is stated as a percentage beside each topic. I borrowed some idea from George Polya's How to Solve It Thoroughly Understand the Problem (30%) When encountering hard problem , you need to deeply understand the problem at hand. Take a paper and list down all known facts and data and what the question is trying to find. Sketch out the problem if applicable. Visualize the problem in your head. A lot of times, we only have to understand the problem well, then the solution will obvious. Have a Plan (20%) You need to have an outline of how you are going to tackle the problem. You need to have a logical pathway that will ultimate produce outcome (nothing to do with coding syntax yet). Without a plan, you are just randomly poking around and got lucky. No hard problem ever gets solved without a plan. Plan using pseudo-code, pen & paper or flowchart. Use wh...
5 comments
Read more

Sharing my Weakness

It makes sense to know about your weakness and do something about it. Here are my known weaknesses uncovered during my time in Launch School. 1. I don't like to refactor my code   - Your first draft will not be perfect. It works but it may not be efficient/readable/best practices. You final code will almost always be better than your first draft. - It is easier to separate the task between writing code that works and refactor later to make it efficient/readable/best practices. - If you refactor your code often, over time you will discover your bad habits and change it. 2. I don't like to read other people's code - There are more good programming practices in other people than in you (especially for beginners like me). - To be good , you need to know more than one pathways to solve a programming problem (and there are always more than one way). Then you can judge their merit. - Reason for dislikes    1. It is considerably harder to read code than to write one (...
1 comment
Read more

Static vs Relative vs Absolute vs Fixed

Static: the default position. Everything starts from top to bottom nicely according the document flow. Relative: still within normal flow of document. But accept offset position, relative to its original document flow position Absolute: out of normal flow. It doesn't interact with elements around it anymore. The reference point will be parent element that has relative positioning, if not, reference body element. Accepts offset position Fixed: out of normal flow. The element sticks to a corner of the page even if user scrolls. Reference the windows view.
Post a Comment
Read more