Earlier quoted context omitted.
Probably, as that doesn't seem like a good reason.
Quite. But how much effort they put in their website and documentation is somehow important to me. Then again, Ruby projects always look glamorous while Haskell projects (just an example for an exotic language) look like some HTML document someone wrote 10 years ago on an university computer. Ember.js in comparison has a certain glow to it. Especially with that weird mascot.
Diving into AngularJS
31–40 of 48 posts
Re: Diving into AngularJS
#32Am I the only one who dismissed AngularJS by the fact that they use a nearly unmodified bootstrap design?
Re: Diving into AngularJS
#33Hey Andy, please consider choosing a more readable font for your blog. I would love to read this article, but the thin font is hurting my eyes.
Thanks for the feedback - I've been wondering about this for a while and you're right. It's just finding something that will work well!
Re: Diving into AngularJS
#34Re: Diving into AngularJS
#35Earlier quoted context omitted.
What do you wish you knew about writing directives then that you know now? Or what did you find confusing? I am currently writing a book on Angular and would like to know. I remember I had a lot of trouble on how to write a reusable component defined in a partial, and what to pass into the directive constructor.
Hey Kevin, this isn't about directives but about RESTful services and $resource. I started learning how to use AngularJS yesterday and all of the examples that I've found on it are confusing to me and seem to do it in different ways. I've seen somebody do it by calling myModule.factory. I've seen an example on Stackoverflow that says all you need to do is something like var Todo = $resource('/api/1/todo/:id');. I'm n…
Angular made a tutorial video on building a Twitter search app that may be helpful: https://www.youtube.com/watch?v=IRelx4-ISbs
Re: Diving into AngularJS
#36The more I use Angular, the more I love it. I like how it's really easy to get started with it. Just avoid writing your own directives right away, that's still the one part that is super confusing (although powerful).
What do you wish you knew about writing directives then that you know now? Or what did you find confusing? I am currently writing a book on Angular and would like to know. I remember I had a lot of trouble on how to write a reusable component defined in a partial, and what to pass into the directive constructor.
It's been a few months, but I remember being confused by "compile" vs "link". I had a hell of a time figuring out which one I needed to use. I also was confused by the passing in of parameters, with weird syntax like "@", and "=" prepending the parameters.
One thing that I tried doing, that I figured would be common, was to access a model specified by ng-model, and to access the controller's scope. But even that was really confusing.
Re: Diving into AngularJS
#37Re: Diving into AngularJS
#38I have been wondering if I should look into AngularJS but I'm a bit worried about it's future given Google also has Dart which seems to be competing with it, or am I wrong? We all know what Google is like when it comes to closing stuff down.
Re: Diving into AngularJS
#39I have been wondering if I should look into AngularJS but I'm a bit worried about it's future given Google also has Dart which seems to be competing with it, or am I wrong? We all know what Google is like when it comes to closing stuff down.
Re: Diving into AngularJS
#40Hey Andy, please consider choosing a more readable font for your blog. I would love to read this article, but the thin font is hurting my eyes.
Thanks for the feedback - I've been wondering about this for a while and you're right. It's just finding something that will work well!