I actually had attempted to use players.at(index) but was getting weird results and went with the playerViews array just because that worked. That documentation link will help. 

On Dec 17, 2013, at 8:58 PM, Joe Fleming <notifications@github.com> wrote:

> In public/js/main.js:
> 
> > +
> > +      this.players = new App.Players();
> > +      for (var i = 0; i < players.length; i++) {
> > +          currentPlayer = players[i]; // cache
> > +
> > +          // set default fields on the player models
> > +          currentPlayer.set('slot', i);
> > +          currentPlayer.set('score', 0);
> > +          currentPlayer.set('turn', 0);
> > +
> > +          // set player view with the model
> > +          var playerView = new App.PlayerView({
> > +              model: currentPlayer
> > +          });
> > +
> > +          this.playerViews.push(playerView);
> I'm not really crazy about tracking the views this way. Models, sure (though, it would be easier to just track the collection and get the models that way). Later in the code, you're just using the Views to pull out the Models anyway, you can do the same thing from the players Collection using at
> 
> —
> Reply to this email directly or view it on GitHub.
>