can.Component now is a perfect way do create completely functional widgets of any kind, it brings quite simple and structured approach to implement MVC architecture. Your app is actually an upper level widget, and you should use can.Component to structure it. It actually contains can.Control in itself.Auth is getting created at the App Level, but I am still struggling with what an App is now... a Component or a Control, I've been using Control, but making the root object a Component has some advantages (such as parent scope and <MyApp>)
↧
Re : Should I use can.Model or can.Map?
↧