Registration.Form = SC.Record.extend(
{
childRecordNamespace: Registration,
authors: SC.Record.toMany(‘Registration.User’, {nested: true}),
…
}

Registration.User = SC.Record.extend(
{
type: “User”,
firstName: SC.Record.attr(String),
lastName: SC.Record.attr(String)
…
}

var user = Registration.store.find(Registration.loginController); // No problem, store retrieves my user

// First attempt:
var form = Registration.store.createRecord(Registration.Form, {authors: []});
form.get(‘authors’).pushObject(user) // => Object
form.getPath(‘authors.length’) // => 1
form.get(‘authors’).objectAt(0) // => undefined, what??

// Second attempt:
var form = Registration.store.createRecord(Registration.Form, {authors: [user]});
form.getPath(‘authors.length’) // => 1
form.get(‘authors’).objectAt(0) // => Object
user.get(‘email’) // => ‘myemail@host.com’
form.get(‘authors’).objectAt(0).get(‘email’) // => null, DAMN!!!

form.getPath(‘authors’).objectAt(0).set(‘email’, ‘anothermail’) // => SC.Error:sc31:Internal Inconsistency (-1)
form.get(‘authors’).objectAt(0).set(‘email’, ‘ooo’) // => Object
form.get(‘authors’).objectAt(0).get(‘email’) // => null, Men, I am lost!

I am trying to recreate the photos application using Sproutcore 1.0.
In that application I would like to show the photos grid using a custom view that I will create and to use it as exampleView of the GridView. The problem is that I can’t figure out how to bind each photo model item to the custom view created by the grid.

Thank you,
Ido.

If you are going to do a very simple straight forward application it is probably better to use the rootresponders like in /sproutcore/apps/tests/states…

The implementation that I used and wrote about is for most complex applications that need to keep track of parallel states, history states and complex substates.
Looks like you have a good grasp of what is going on in the state charts… it is really hard to understand what to do until you start to actually code an app with a state chart. The idea is all ‘actions’ take place on the global application namespace. So in your application if you have a ‘target’ and ‘action’. ie Buttons, dropdowns etc that trigger events on you app. Then you are able to sort out based off of where you are on the application (state) to trigger events or processes.

if you would like, I can set up a web meeting to show you some advanced stuff with state charts that we are doing…jsut send me an email.

Evin (etgryphon)

After browsing through the code, this is how I understand it.

main.js
——–
main() {
// set initial state of application
ContactsTool.goState(‘a’,1);
}

core.js
——-

ContactsTool StateChart object initialized here, contains function for each app. state (as per statechart diagram)

// ContactsTool.goState(‘a’,1); becomes a call to state handler function ContactsTool.goStateA1
// the initial login screen is loaded (see login.js)
goStateA1: function() {
//login screen
this.set(‘mainView’, ‘ContactsTool.loginPage.mainView’);
}

login.js
——–
Custom page is created with a button. Clicking the button results in the action ’submitLogin’ on the target ContactsToll (StateChart)
Thus the StatChart will handle this action

Back in core.js
—————-
//core actions

submitLogin: function() {
var handled = NO;

switch(this.state.a){
// if I came from state A1 (initial login screen)
case 1:
// I will go to state A2
this.goState(‘a’,2);
handled = YES;
break;
}
// error! I shouldn’t end up here. Only valid entry point is from initial login screen!
if(!handled) console.log(‘ContactsTool#submitLogin Action not handled in state %@[%@]‘.fmt(‘a’,this.state.a));

–
and so on from here…

Any comments?