Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve been digging into EmberJS for one day :).
I’ve followed several examples. Some examples used ArrayProxy while others used ArrayController. I looked at the unminified source code and..guess what…Ember.ArrayController is simply extending Ember.ArrayProxy, but there’s no extra methods or features in ArrayController.
So..my question is..why do we have two same classes?
There is no difference between the two classes.
It’s for all of us who are coming from SproutCore 0.9.x, 1.x and early SproutCore 2 betas and were just use to the name
ArrayControllerI think. I’d recommend using ArrayProxy in case the core team decides to depreciate the one line of code that makes ArrayController possible 🙂