Initially, my app had only a main UI with navbar and sidebar, plus a content area represented by an ng-view where various partials get switched in and out. Now I am adding simple user registration and login forms (which don't include any of the navbar/sidebar stuff...and they are not modal popup dialogs.) The app could ultimately become fairly complex so I want to adopt good design principles early.
Question: Should the login UI views be separate HTML files with their own ng-app directives and route structure? Or should they be partials linked toone and only ng-view in one single page app? The single-page approach seems kind of non-modular and will force me to rework the ng-view to include the navbar and sidebar content. (with ng-include?) On the other hand, I don't know if I will encounter problems down the road with the multi-page approach perhaps due to communication of information between the apps. What is the best practice for doing this? 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.
