Personally, I use ui-router. I defined a top-level ui-view (called app), into which I placed a ui-view for header, footer, and body. Substates of app correspond to each "page" of the application, defining new content for the body view, and the menu bar and footer stay the same.
On Thu, Sep 25, 2014 at 2:01 PM, mark goldin <[email protected]> wrote: > I am redesigning an application that has the following structure: > > Main screen with a drop dawn menu on a top. Each menu choice opens a full > screen page underneath the menu. Nothing special. How should I architect my > app based on Angular SPA concept? > Here is what I've got so far: I have an html page (like a main page of one > menu choice) but it has the menu in itself. Now I want to move the menu to > an application main page. How I go about creating and managing states? > Right now the html page creates states and loads content. Should my new > application main page create states for menu choices pages or (looks more > comprehensible to me) each page will create its own set of states? Any docs > about it? > > Thanks > > -- > 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. > -- 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.
