In so many subtle ways I find myself fighting with router logic with ember. It may be the mental model I stubbornly cling to, but personally I am finding that thinking about URLs first is more difficult than it seems at first blush.
I will fully admit that I may just be over thinking it, and per Yehuda’s point that this might be an indication of doing something wrong.
I am wondering if anybody has good reference examples that demonstrate complex UI design in practice with ember. By “complex” I mean cases where you have nested view hierarchy and multiple models on a page, and perhaps aggressive use of components to encapsulate view logic, and ultimately a lot going on under a specific route or route state.
Looking for examples to get my mind out of its stubborn point of view and expand my thinking to be more idiomatically ember.
Sorry for the broad question. To be more concrete ideal examples would include
- compelling and creative use of
modelForas well as
- multiple components on a page
- visual representation of application and route state in a navigation menu, hud, aside, breadcrumb, or other status area on the page.
- condensed jump menu that lets you quickly move around items in a collection and between router states
- master/detail view with nested elements within the detail
- at the model data layer heavy use of composition from lower more basic models/classes, polymorphism, as opposed to classical inheritance and hierarchy.
- creative use of filters and computed properties.