Ok, interesting, I'm tossing up which direction to head here too. So, you are saying that you are choosing browserify to manage the module dependancies over angular. The fact that angular DI all ends up in 1 namespace has always bothered me, so, maybe this is a good choice. It is a bit of a dramatic steering away from common angular formatting however. I'd be interested in others opinions here.
On 24 July 2014 00:43, Axel Hernández Ferrera <[email protected]> wrote: > Hi Tony > > Thank you for your answer. > > I am trying to be pragmatic with the dependency injection. I don't want > all my classes being part of the angular injector unless there is a reason > for that, and the only reason it came to my mind if that a class has a > dependency of something from angular (ie $timeout). The benefits to not > couple the business logic classes to angular it's share the code with the > server. > > On Wednesday, July 23, 2014 10:07:12 PM UTC+1, tonypee wrote: > >> Firstly, I really like the style, this would be great (es6). >> >> Im unsure about how the modules manage the dependencies themselves. Ie. >> the reference to 'Counter' is not dependency injected. It seems like >> browserify is managing all dependencies here. Also how the app needs to >> then bring all of these classes into the app at app level. >> >> To incorporate with the angular module system more (browserify modules >> can return angular modules) might be an approach. Im not sure where the >> sweet spot here is tho - im actually looking to integrate browserify into a >> new project, so am very interested in this. >> >> Of notice, I just watched this (which you've probably seen): >> https://www.youtube.com/watch?v=NTPutZ99XWY This seems to integrate more >> with the angular module system >> >> >> >> On 23 July 2014 10:12, Axel Hernández Ferrera <[email protected]> wrote: >> >>> What is your opinion about this example of angular.js + es6 classes ? >>> >>> https://github.com/axelhzf/angular-es6 >>> >>> -- >>> 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. >>> >> >> >> >> -- >> Tony Polinelli >> >> -- > 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. > -- Tony Polinelli -- 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.
