Sun, Jul 26, 2015
It’s well known how ui-bootstrap supports modal windows. These modals don’t have any URL and cannot be accessed by URL, though. This is very good, because they should stay as the main view subview only, don’t mess with the browser history and first and foremost they shouldn’t kill underlying main view controller, what would reset its current state (like filters applied, pagination, etc). This would be a problem using URL-based modals, especially with ui-router which seems to be a standard for now.
Sun, Sep 21, 2014
It is a common case in AngularJS to have some model loaded on the main view (like list of objects) and to use these objects in other controllers (like the object details view). Usually it’s done by holding the reference of the list object in other controller scope, to interact with this reference. Until these both objects point to each other (both references point to the same object) it’s very fine. The changes from the details controller are reflected in a list and contrarywise.
But I frequently come across the situation where at least one of these objects is refreshed from the server (eg. in async comet event) and this relationship is lost. A lot of case-by-case code is required to be written to support such instances on the client side.
Fri, May 9, 2014
Suprisingly for me the controller state in AngularJS is not preserved between the controller invocations. I at least expected an option to switch it on and off on demand. For the classic application it was difficult to achieve that we may restore the state for a given view (eg. to be on the same page as we were leaving the view), what sounds great for me from the application usability point of view.