[AngularJS] Re: Courious 3 Web development in same domain with Angularjs. Ideas how you would structure the development in Angularjs

2017-06-07 Thread Rafa

>
> Sorry, I hope not to bother you, but in case you know any idea where I could 
> look or start to implement this idea in angularjs 
>
>  

> https://groups.google.com/forum/?hl=es#!topic/angular/PfVdwVD2KZY 
>
> I appreciate all the help you have given me so far and I do not want to 
waste your time, but just in case you even knew something related to this 
idea. 

Thank you  and best regard

>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to angular+unsubscr...@googlegroups.com.
To post to this group, send email to angular@googlegroups.com.
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.


[AngularJS] Re: Courious 3 Web development in same domain with Angularjs. Ideas how you would structure the development in Angularjs

2017-05-19 Thread Sander Elias
Hi Rafa,

I have done a load f angular apps, and usually, you don't need a run 
statement at all. 
In your case, you can encapsulate the login in its services, and summon the 
one you need on instantiation of the top component for the part you are 
activating. 
There is no issue there, and you can maintain as many login-streams as you 
need. By building your app with components that make sure they encapsulate 
all their dependencies.

Regards
Sander
 

-- 
You received this message because you are subscribed to the Google Groups 
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to angular+unsubscr...@googlegroups.com.
To post to this group, send email to angular@googlegroups.com.
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.


[AngularJS] Re: Courious 3 Web development in same domain with Angularjs. Ideas how you would structure the development in Angularjs

2017-05-19 Thread Rafa
Hi Elias, I see very reasonable what you say and I'll try to follow your 
idea given the obvious advantages of just maintaining a single development. 
I see now this way more clear.

A doubts if I may:
 
 In angularjs developments that I have done so far I have used a lot of 
app.run () to do very global tasks.

In this case two of the developments have their own login status or not 
logged in according to their own form (both login are different, ie against 
different scripts) so in the bundle it all up in 1 version I musn't put 
very much code in app.run() and try differentiate very well every status in 
it for every possible mode of operation of the app and do more in every 
controller view

But as you say, are very shorts and simple developments and this is very 
easy.



Than you again for yor help and patience

-- 
You received this message because you are subscribed to the Google Groups 
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to angular+unsubscr...@googlegroups.com.
To post to this group, send email to angular@googlegroups.com.
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.


[AngularJS] Re: Courious 3 Web development in same domain with Angularjs. Ideas how you would structure the development in Angularjs

2017-05-19 Thread Sander Elias
Hi Rodriguez,

I decided not boundle it all up in 1 SPA because wanted keep very simple 
> every spa webapp. 

Well, each page has its layout and some form of authentication in common. 
Also, you can use the router to take care of the 'different' pages. If 
those are loaded in different tabs, they are separate instances no matter 
what.  
Especially if you are talking abut super simple views in most pages, it 
makes sense to bundle it up, and deal with a single instance, instead of 
repeating the work of creating a repo, Align tooling and so on. Set up CI 
and testing. Etc..

Don't get me wrong, you can separate them, but you are just adding to your 
unneeded things to your workload,
The ng1 router is well suited for things like this!.

Regards
Sander

-- 
You received this message because you are subscribed to the Google Groups 
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to angular+unsubscr...@googlegroups.com.
To post to this group, send email to angular@googlegroups.com.
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.


[AngularJS] Re: Courious 3 Web development in same domain with Angularjs. Ideas how you would structure the development in Angularjs

2017-05-19 Thread Rafa
Hi Elias,

I appreciate your contribution because reassures me and supports seeing 
that someone sees it more or less like me and that my idea is acceptable.

I decided not boundle it all up in 1 SPA  because wanted keep very simple 
every spa webapp. 
So thought creating 3. They really will not have anything in common and yet 
I could be involved with possible internal states.
Each one opens in different tab with its own states and possibly would use 
router for a pair possible views in each one. Except for the administration 
that would have registration forms, edition and listings.

 Thank you very much.

-- 
You received this message because you are subscribed to the Google Groups 
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to angular+unsubscr...@googlegroups.com.
To post to this group, send email to angular@googlegroups.com.
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.