Hi, I'm building an search application flow with Angular. Being an Angular newbie, I've stumbled on a couple of design issues in the process. Here's some background of the application flow:
The user fills in a search form and is presented with search results. If the initial search terms are ambiguous, the user is asked to disambiguate the terms by selecting from a list of additional search criteria before the search results are rendered. This is mobile app and due to screen size limitations the results page allows users to drill down to search result details in separate views. I was planning to implement the search form, results list and result details as separate views, with one controller per view. Is this a reasonable design with Angular? How should the disambiguation step be implemented with Angular? When a view transition is triggered by clicking on an anchor, can the app first issue a backend request and after receiving the results decide whether to veto the view transition in order to request disambiguation from the user? Or can the view be programmatically changed in a controller? Which are my options for passing model data from a controller to another? I'm using anchors for triggering transitions between views, so search form parameters can be passed as URL parameters, but what about passing data from results list model to result details model? marko -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
