mirror of
https://github.com/kbparagua/paloma
synced 2023-03-27 23:21:17 -04:00
commit
78259f4428
1 changed files with 1 additions and 1 deletions
|
@ -12,7 +12,7 @@ It is now simpler and more flexible. The old callback thingy paradigm is replace
|
||||||
Previously, there are generators that create Paloma files, and these files are written in vanilla javascript. Because of that there are some users who are requesting for coffeescript setup. Now since there are no generated files programmers can write their code either by using vanilla javascript or **coffeescript**. Yay!
|
Previously, there are generators that create Paloma files, and these files are written in vanilla javascript. Because of that there are some users who are requesting for coffeescript setup. Now since there are no generated files programmers can write their code either by using vanilla javascript or **coffeescript**. Yay!
|
||||||
|
|
||||||
### Controller and Router
|
### Controller and Router
|
||||||
The new paradigm is pattered after Rails Controller and Routes, so it is easier to grasp than the old callback paradigm. Basically, you have a Paloma Controller that is responsible for processing requests made from Rails Controller. While the Router is responsible for telling what Paloma Controller handles what Rails Controller, or what Paloma Controller's action handles what Rails Controller's action.
|
The new paradigm is patterned after Rails Controller and Routes, so it is easier to grasp than the old callback paradigm. Basically, you have a Paloma Controller that is responsible for processing requests made from Rails Controller. While the Router is responsible for telling what Paloma Controller handles what Rails Controller, or what Paloma Controller's action handles what Rails Controller's action.
|
||||||
|
|
||||||
|
|
||||||
### How about Model and View?
|
### How about Model and View?
|
||||||
|
|
Loading…
Reference in a new issue