laravel4cookbook

Real Time Chat 175
18 App.ApplicationAdapter = DS.FixtureAdapter.extend();
19
20 // 5
21 App.Message.FIXTURES = [
22 {
23 "id" : 1,
24 "user" : "Chris",
25 "text" : "Hello World."
26 },
27 {
28 "id" : 2,
29 "user" : "Wayne",
30 "text" : "Don't dig it, man."
31 },
32 {
33 "id" : 3,
34 "user" : "Chris",
35 "text" : "Meh."
36 }
37 ];
.
This file should be saved as public/js/shared.js.
If you’re an EmberJS noob, like me, then it will help to understand what each piece of this script is
doing.
1. We create a new Ember application with Ember.Application.create().
2. Routes are defined in the App.Route.map() method, and we tell the application to equate the
path / to the index resource.
3. We define a Message model. These are similar to the Eloquent models we have in Laravel 4,
but they’re built to work with EmberJS (and are obviously on the client-side of the application).
4. We specify a fixture-based data store for our application. We’re using this, temporarily, to fill
our interface with some dummy data, but we’ll add a dynamic data store before too long…
5. Here we add the fixture data. Notice that, in addition to the two model fields we defined, we
also specify ID values for the fixture rows. This data is used to single out individual Message
objects.
When you browse to the base URL of the application; you should now see an acceptably styled list
of message objects, along with a heading and input form. Let’s make it dynamic!