@_henni wrote:
Hi, currently I am struggeling to get my head around the current architecture of Ember. As I understand Ember was MVC in the past but now is DDAU. In reference to this always routable components are mentioned but they do not exist, yet?! I am working on an Application, where different functional parts have to communicate to each other but are in the same route. As I understand components are isolated to the surrounding, which makes it complicated for me. As I don‘t need the parts again in any other part of my Application (only 3 or 4 routes), I decided the following: -Different routes with own controller and template -> each route represent one core functionality -One Model injected into routes or service? -Service for general data handling So this works like a charm, is easy and clear. Why should I use components? Do you see any problems on this approach? Sure, I could pack my whole controller content in a component but I think thats not the way to do it. What would this be called, what I am doing? Thanks!
Posts: 1
Participants: 1