Hello Vaibhav,

Thank you for the link regarding the folder structure, but as I said, that 
is now what I need at the moment. I will read it anyway. I knew about John 
Papa's recommendations about angular, that is always a good reference. 

2. You should look at how your application will behave. If it is a single 
> page application, you might want to use routing to break components of a 
> page into sections. A section will be displayed when user accesses the url 
> associated with it. For instance in the pseudo html markup you shared, you 
> might have three routes:
> a. create-accounts-section
> b. results-section
> c. configuration-section
>

My app is indeed a single page application. I did not used routes because 
it was just a tabbed interface with three tabs: one form to fill in, a tab 
with results of that form submission and an application configuration tab. 
With such simple structure do you think that deserves to use routes? I have 
no idea how normal is this in angular world, so I would like to hear your 
answer about this.
 

>
> You may use ui-router <https://github.com/angular-ui/ui-router> to 
> achieve this. Index.html will be composed on these sections using ui-view. 
>

Currently each section communicates with the others making use of services. 
Will it be the same way using ui-router?
 

>
> If your application is a big monolithic page, like a content heavy site, 
> you may proceed with the way you are doing right now, i.e. using server 
> side processing to compose index.html. 
>

No, my application is not that kind of site, and I'm not using server side 
processing to compose the index. I use a gulp task to compose the index, 
that's true, but then I will deploy that index file as a SAP.

Many thanks for your comments. 

-- 
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.

Reply via email to