Let's consider you need to use it for multi page application,
What will be best architecture (considering angular controllers, modules, directives, services/factories/validation)
Also I believe you have to use routing to route request one to other page using angular routing
Sent from my iPhone
> On Mar 9, 2016, at 8:45 AM, Aalap Shah <shah.aa...@gmail.com> wrote:
>
> As we all know angular js is one of the best option when you design for single page applications.
>
> Let's consider you need to use it for multi page application,
> What will be best architecture (considering angular controllers, modules, directives, services/factories/validation)
>
> --
> You received this message because you are subscribed to the Google Groups "Elite Techie Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to elite-techie-group+unsub...@googlegroups.com.
> To unsubscribe from this group and stop receiving emails from it, send an email to elite-techie-gr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Elite Techie Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elite-techie-group/U6AYOAj6n3M/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elite-techie-gr...@googlegroups.com.
UI layer will split here....UI layer and UI services layer....UI will be just html and JavaScript behavior files for each page and UI logic layer will have common scripts such as module services directives....
Bhavin suggestion is Angular Factory and Services difference....Whether you want single instance or multiple...based on that Angular provides 2 approach on Angular Services and Factory....
Agreed, Controllers do not talk directly or through services....but through modules...
Also,
Controllers should not talk to each other...else they are breaking design....it is simple...there should not be any scenario where they need to talk each other....
UI router is routing framework...similar to RequireJS but with some differences....such as partial views and div loading etc...
Nopes...you are breaking the design concept...Controllers cannot communicate with each other....parent child controller concept is not for this purpose...
Let me put it this way.... In Asp.net MVC, an action can take us to other controller...and alongwith it you can pass json, string or etc. But you cannot create instance of another controller and access its members...it doesn't stop but not designed for that....definition of controller is bound to its models and views....
Angular is MVW, whatever doesn't literally means do whatever..... ;-) just kidding on a lighter note...take it easy... :-)
One more thing, I don't understand this scenario....why would one controller needs other controllers instance....this will not even required in partial view scenario....
I agree that....that is not within the scope of rootscope ;-)
Swami, still learning .... Waiting for Angular 5 ;-) :-) We never said that...In this group we only post based on experience...we were stretching tech boundaries and learning new stuff and sharing and clearing doubts.... Remember covariance and contravariance....we didn't implement in past and till date....but we were learning...so now on...this reply will only put additional weight on other members...please enlighten our knowledge pool with your magical mind... ;-)
I am on python django pandas R eclipse jira qunit karma djangocms but still not losing touch with Billu saheb...jaag jao mitra :-)