[AngularJS] Re: Angular 2.0 ChangeDetection not getting trigerred when ActiveX (Object Tag) is present

Hi Arvind, So you are manipulating your data inside Angular. Normally you don't need to force changeDetection then. Can you show your issue in a plunk? Regards Sander -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsu

[AngularJS] Re: Angular 2.0 ChangeDetection not getting trigerred when ActiveX (Object Tag) is present

To be frank ActiveX components does not raise any events ( it is currently just present , doing nothing . ) In my code my ng components I use ngFor* directive ( bound to an array of lets say strings) . when i add something to the array i was expecting changedetection to kick off , but it does

[AngularJS] Re: Angular 2.0 ChangeDetection not getting trigerred when ActiveX (Object Tag) is present

Hi Arvind, For this use-case, you need to look into zoneJS. When you go down this route, you have to realise, there is no true change detection anymore. Instead of that, Angular monitors all things that could cause change. (user-generated events, network, storage etc..) When it detects such a

[AngularJS] Re: Angular 2.0

Angular 2.0 is not Angular at All !! I wish they issued another technology and left the version 1.X grow up normally, I think these changes are wrong (statistical) To Development Team, > > Today I read about Angular 2.0. ( > http://ng-learn.org/2014/03/AngularJS-2-Status-Preview/) > As we menti

[AngularJS] Re: Angular 2.0 JavaScript Docs

No :( I've read the 5 minute tutorial but looking to expand into the later docs. On Sunday, March 6, 2016 at 10:09:22 PM UTC-8, Long Field wrote: > > https://angular.io/docs/js/latest/quickstart.html >> > Is this you are looking for? > -- You received this message because you are subscribed to

[AngularJS] Re: Angular 2.0 JavaScript Docs

> > https://angular.io/docs/js/latest/quickstart.html > Is this you are looking for? -- 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 angular+unsubscr...@googlegro

Re: [AngularJS] Re: Angular 2.0 for a commercial application

Hi, Just back in from #ngnl2016. @daniel Angular 2 did reach beta level a while ago, we are now on beta-6. That means that the team will try to prevent any more breaking changes. You can start using it now for little/not critical projects. But don't expect a release candidate anytime soon.

Re: [AngularJS] Re: Angular 2.0 for a commercial application

And the point probably is that it is now a lot more sensible to start with angular 2.0 than it was a year ago. Even though it is in alpha you can probably keep up with the updates if you follow the release announcements carefully. tors 18 feb. 2016 kl. 16:48 skrev Günter Zöchbauer : > The release

[AngularJS] Re: Angular 2.0 for a commercial application

The release date will be made public on the release date. Google doesn't provide timelines. On Wednesday, February 17, 2016 at 5:32:47 PM UTC+1, Leonel Gayard wrote: > > It's almost a year since this last reply. > > The NPM package page shows version as 2.0.0-beta6, as I'm writing. > > I think it'

[AngularJS] Re: Angular 2.0 for a commercial application

It's almost a year since this last reply. The NPM package page shows version as 2.0.0-beta6, as I'm writing. I think it's time to ask again, is there a release date now ? -- Leonel On Thursday, April 2, 2015 at 7:26:02 AM UTC-3, Daniel Lidström wrote: > > There's no release date set for Angula

[AngularJS] Re: Angular 2.0 - Shims and/or Polyfills and/or ES5 Transpiling and/or AMD solutions for legacy IE?

Ha ha! Yes, I definitely do charge extra for legacy browser support, though I can't say I enjoy tacking on polyfills. On Monday, July 27, 2015 at 8:27:13 PM UTC-7, Sander Elias wrote: > > Hi John, > > There will be a compiled version available, right in github, so you don't > have to compile any

[AngularJS] Re: Angular 2.0 - Shims and/or Polyfills and/or ES5 Transpiling and/or AMD solutions for legacy IE?

Hi John, There will be a compiled version available, right in github, so you don't have to compile anything yourself. For the IE9 and 10, (I feel I must put safari in here too!) support, as long as we as developers keep them afloat, by putting in lots of extra effort (read $$$), there is littl

[AngularJS] Re: Angular 2.0 - Shims and/or Polyfills and/or ES5 Transpiling and/or AMD solutions for legacy IE?

Thanks for the reply Sander. TypeScript compilation certainly sounds like a viable solution and something I'll have to prove out. I just really hope this is something the Angular team addresses a little clearer. Hopefully the Angular Material team does likewise for the 2.0 stuff as I have been

[AngularJS] Re: Angular 2.0 - Shims and/or Polyfills and/or ES5 Transpiling and/or AMD solutions for legacy IE?

Hi John, Angular 2 is build using typescript. That compiles to ES5 (and even back to es3), so for the JS part, it will run mostly everywhere. You can run the test-suite against IE9 and see what comes up. You can then choose to file issues on that to the github. If those issues ar small and wide

[AngularJS] Re: Angular 2.0 - Shims and/or Polyfills and/or ES5 Transpiling and/or AMD solutions for IE10 and IE 9? Is IE11 really the only version supported?

Updated the title to be a bit more specific. -- 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 angular+unsubscr...@googlegroups.com. To post to this group, send email

[AngularJS] Re: Angular 2.0 - Shims and/or Polyfills and/or ES5 Transpiling and/or AMD solutions for IE10 and IE9? Is IE11 really the only version supported?

Updated subject to be more explicit. On Tuesday, July 21, 2015 at 6:59:31 PM UTC-7, John Livingston wrote: > > *Intro* > > This may be a bit premature since *Angular 2.0* is still in alpha and we > likely won’t have any news about release dates or betas until the October > conference. However, g

Re: [AngularJS] Re: Angular 2.0 Dependency Injection between Services

Last I heard, this was working as intended . Still feels strange to me, though. On Wednesday, June 17, 2015 at 3:02:19 AM UTC-5, Georgios Diamantopoulos wrote: > > Still seeing this in alpha 26. Any news since this last post? > > > > On Sunday, A

Re: [AngularJS] Re: Angular 2.0 Dependency Injection between Services

Still seeing this in alpha 26. Any news since this last post? On Sunday, April 26, 2015 at 9:52:24 PM UTC+3, David Lesage wrote: > > I agree -- and I'm not convinced that it's not a bug. I feel like di.js > should be able to resolve those child dependencies without needing to have > them injec

Re: [AngularJS] Re: Angular 2.0, TypeScript and Traceur

Thanks Sander! On 16 May 2015 at 07:21, Sander Elias wrote: > Hi João, > > Short answer: yes. > > Regards > Sander > > -- > You received this message because you are subscribed to a topic in the > Google Groups "AngularJS" group. > To unsubscribe from this topic, visit > https://groups.google.c

[AngularJS] Re: Angular 2.0, TypeScript and Traceur

Hi João, Short answer: yes. Regards Sander -- 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 angular+unsubscr...@googlegroups.com. To post to this group, send email

Re: [AngularJS] Re: Angular 2.0 Dependency Injection between Services

For singletons I will use (for now) this solution: http://twofuckingdevelopers.com/2015/04/angular-2-singleton-service/ About requiring parent component for communication I did not try it but maybe this could help: http://unobfuscated.blogspot.be/2015/03/posts-from-edge-injecting-parents-into.

Re: [AngularJS] Re: Angular 2.0 Dependency Injection between Services

I agree -- and I'm not convinced that it's not a bug. I feel like di.js should be able to resolve those child dependencies without needing to have them injected. I've seen it work that way, at any rate. You can just run injector.get(TopLevelComponent) and all child level dependencies can be res

Re: [AngularJS] Re: Angular 2.0 Dependency Injection between Services

Thank you, it's a lit a bit strange to include everything in the @Component injectables, but its working like this. Milan On Saturday, April 25, 2015 at 7:57:33 AM UTC+2, David Lesage wrote: > > Take a look at this plunker: > http://plnkr.co/edit/UyNe7a4wD3OWXGTyWlAI?p=preview > > I took one of

Re: [AngularJS] Re: Angular 2.0 Dependency Injection between Services

Take a look at this plunker: http://plnkr.co/edit/UyNe7a4wD3OWXGTyWlAI?p=preview I took one of the templates from the angular website and extended it -- One thing to note (and I'm not sure if this is intentional or not, doesn't seem to be necessary with di.js), I had to include @Component injectab

[AngularJS] Re: Angular 2.0 Dependency Injection between Services

So this should work or did I miss something ? http://plnkr.co/edit/ehV8PojejoTk1h28VsPb?p=preview Milan On Friday, April 24, 2015 at 10:34:02 AM UTC+2, Milan Pevec wrote: > > Thank you for the answer and yes I see the same error.. > > Milan > > On Thursday, April 23, 2015 at 6:50:58 PM UTC+2, D

[AngularJS] Re: Angular 2.0 Dependency Injection between Services

Thank you for the answer and yes I see the same error.. Milan On Thursday, April 23, 2015 at 6:50:58 PM UTC+2, David Lesage wrote: > > Yes and no -- My next step was to update the Angular2 code by grabbing it > off of github, followed by grabbing all of the dependencies myself > (SystemJS, Trac

[AngularJS] Re: Angular 2.0 Dependency Injection between Services

Yes and no -- My next step was to update the Angular2 code by grabbing it off of github, followed by grabbing all of the dependencies myself (SystemJS, Traceur, etc) and starting from scratch. I eventually got it into a state where all of the injection *mostly* worked, but I was getting an issu

[AngularJS] Re: Angular 2.0 Dependency Injection between Services

Hi David, did you maybe find the solution ? Regards, Milan On Friday, April 3, 2015 at 7:01:37 PM UTC+2, David Lesage wrote: > > Absolutely, that looks perfect. Is that syntax functional, or just > proposed? I'm wondering if I need a newer version of Angular2 than what is > included with the q

[AngularJS] Re: Angular 2.0 Dependency Injection between Services

Absolutely, that looks perfect. Is that syntax functional, or just proposed? I'm wondering if I need a newer version of Angular2 than what is included with the quickstart to get that to work. I'm currently not having any luck with the following: import {DispatcherService} from 'services/Dispatc

[AngularJS] Re: Angular 2.0 Dependency Injection between Services

Hi David, You mean you want somethig like this: export function threeStrikes (req:Request|string) { return this.http(req).retry(3); } @Inject(threeStrikes); export class MyComponent { constructor(threeStrikes) { threeStrikes('[http://foo.bar](http://foo.bar/)').subscribe(onNext, onErr

[AngularJS] Re: Angular 2.0 for a commercial application

There's no release date set for Angular 2. You're *much* better off doing your SPA with Angular 1. On Thursday, 2 April 2015 11:48:40 UTC+2, Shivanka de Silva wrote: > > Hi, > >Would Angular 2 be stable enough to be used in a client SPA application > ? version u all have s alpha and would

[AngularJS] Re: Angular 2.0

As it takes some time to get into a new framework (not only scratch the surface) I would say, stay with what you are unless you are sure that Angular 1.3 is that much better for your case. Otherwise: if you are writing good code in Angular much of it will end in a data framework (angular-data?)

Re: [AngularJS] Re: Angular 2.0

New technology is always coming out. Angular has a wide user base, and will be used far into the future. If it suits your needs, then I'd say, use it. It will be good experience for learning the skills you might need for angular 2, or any other modern framework. On 24 February 2015 at 03:22, wrot

Re: [AngularJS] Re: Angular 2.0

Here goes my logical reasoning: I evaluated Angular 1.3 for my next project. I built a prototype app with it and I like it. So I want to go forward with it... But wait: everything I will learn about Angular 1.3 I will need to throw away somewhere in 2016 when Angular 2.0 comes out... So my que

Re: [AngularJS] Re: Angular 2.0

You are completely don't got my point. >logical reason to hate Angular 2 I never told that i hate Angular 2. I just told that Angular 2 is not Angular at all, it completely new technology. You could think for example that all angular team decide to develop Meteor 2 instead of Angular. I worryi

Re: [AngularJS] Re: Angular 2.0

Well said, Benoit :) On Wednesday, November 12, 2014 5:49:45 AM UTC-5, Benoit Tremblay wrote: > > Please, for god sake, stop the useless drama and look for the facts. > > 1. They are not going to release Angular 2 soon. Not going to happen in > 2015 for sure. > 2. Their is a big enough community

Re: [AngularJS] Re: Angular 2.0

Please, for god sake, stop the useless drama and look for the facts. 1. They are not going to release Angular 2 soon. Not going to happen in 2015 for sure. 2. Their is a big enough community around Angular 1.3 to fix the critical bugs outside of the core team. 3. They are going to support Angula

Re: [AngularJS] Re: Angular 2.0

>as time invested in yourself, and this isn't lost - it only prepares you for the future. I'm absolutely understand your position and exactly because your position i telling you than you are immature. I will show you couple of examples: 1. You are buying your mobile phone with GSM network suppo

[AngularJS] Re: Angular 2.0

@Tony - Totally agree. The "innovation" on the web came from frameworks and people who worked around all the ugly stuff. And I'm old enough that I have seen lots of innovation ;) Host with dumb terminals. (ugly stuff on clients) Rich clients (PCs) with almost no host. (maintenance horror) Back t

Re: [AngularJS] Re: Angular 2.0

haha. 2002->2009 = 7 years. good work on the counting tony ;P On 12 November 2014 00:41, Tony pee wrote: > Alexey, from your points i gather that you are basically upset about the > time that people have *invested* already in angular 1.x and feel that this > shouldn't be *wasted*. Despite the fa

Re: [AngularJS] Re: Angular 2.0

Alexey, from your points i gather that you are basically upset about the time that people have *invested* already in angular 1.x and feel that this shouldn't be *wasted*. Despite the fact that 1.x isn't going anywhere and therefore there isnt any *loss* involved; I would encourage you to see the ti

[AngularJS] Re: Angular 2.0

I think the major problem is the quick paradigm shift. Take ember. There is a 99% chance that an example on the web is not compatible with the version you are working because the API changes every few minutes (exaggerated *lol*). When you are working with ember you know that the doc you are rea

[AngularJS] Re: Angular 2.0 closed source, in planning, or what

ANGULAR, DART and POLYMER : The Holy Trinity of the Future Web? Dart is a better scripting language for the web of the future. It takes the best of javascript, Ruby, Java and C#, it integrates all those functions that once required dozen of libraries (no more need of JQuery, NodeJs, Modernizr.j

[AngularJS] Re: Angular 2.0 closed source, in planning, or what

>From what I've gathered, development of 2.0 appears to be well on its way, and is starting with some of the components which have been separated out to (hopefully) allow their use outside of angular (perhaps for code sharing with the polymer team et. al?). There appear to be at least three com

[AngularJS] Re: Angular 2.0 closed source, in planning, or what

Hi Adam, Angular 2.0 is in the planning stage, It's discussed by the core team, parts are being build as we speak. There is (as far a I know of) not (yet) a central repository. There are references on how to get involved all over the place, The best way is through the github projects, fork, com