In my own experience, Angular is different enough from everything else that it is *totally* worth going through whatever tutorials you find. I tried diving in (even coming from an EmberJS background) and ended up with infinite loops and failures to properly handle dependency injection.
Then, I stopped trying to build my actual project and went back. I built PhoneCat from the angularjs.org site and watched a number of egghead.io tutorials (I even sprung for the pro membership as there's a lot of good content there). I went from zero to mediocre with Angular in a couple of days. I'm probably still working on mediocre to "meh", with "decent" in my long-term plans. I had the extra handicap of learning javascript for reals as well (I'm an old-school C++ -> Java -> Rails server developer just starting on front-end stuff). So: if I were doing something like this in 48 hours I might personally not pick up an Entirely New Framework for that project. Stick to what you know. But that's project planning advice outside of the scope of this list. But seriously, it looks like somebody else already wrote a prism-formatting directive that's worth looking at: https://github.com/nucleus-angular/prism e On Mon, Jun 16, 2014 at 6:48 AM, Anshul Jain <[email protected]> wrote: > Ok now I got why we need to do build a directive. Thanks I will read > directives from here > > https://docs.angularjs.org/guide/directive > > Will that be enough on directives. Also should I once read the whole > documentation before building my app. Can I do it within 48 hrs.... I am > short on time. > > You can also add your links. > > Thanks again to Sander and Eric :) > > > On Monday, June 16, 2014 3:33:40 PM UTC+5:30, Sander Elias wrote: >> >> Hi Anshul, >> >> Seems you have some more reading to do then ;-P >> >> What happens is, that once prism has replaced the html with the formatted >> code, it breaks the connection that angular needs. >> the {{data}} is tells angular, insert the content of data here, and show >> it. Prism breaks that link, and inserts its own content. >> That is the reason you can't update it anymore. >> >> Have a look at this plunker! <http://goo.gl/N2zVTW> >> >> 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 [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. > -- 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.
