AngularJS MTV Meetup: Best Practices (2012/12/11)

Показать описание

Live from the Mountain View, CA meetup, Miško Hevery discusses the advantages and disadvantages of various design choices when structuring an app in AngularJS, and some of the best practices that we use in our own development.

Some of the topics we'll cover:
- Style best practices that we use in our own projects at Google
- Handling different browsers when writing directives (e.g. IE)
- Comparisons between different ways of structuring your application:
+ using controller vs scope
+ using directive prefix vs namespace
+ using element name vs attribute name vs class

Рекомендации по теме

Комментарии

The actual presentation length is 40 minutes, don't be discouraged by the total time. It's a very, very good presentation and the information in it is still valid today.

dmn

very helpful even a few years later, thank you

jbownzino

56:10 "What's Angular 2.0 going to be like?" LOL!

rickelmonoggin

I am not the fastest, so I will see this a second time before diving into angular without the zen.
Thanks - its very good.

gardsted

Love this video, like 2 years old, but even my grandma would understand Angular from him.

mobiledevtube

"You should group by views since views will be lazy loaded in near future" - Misko in 2012. Anyone know if this is still the plan? I'm thinking they're actually going to do this by module now...

NashvilEric

Really awesome.... When is AngularJs 2.0 will come out.

DrequimaX

He says "Configuration over Convention" but he means "Convention over Configuration"

subashkc

I re-watched this video three times by now. If you work with #angular, that will be very helpful for you.

#codingisfun

AlinaBasova

they always manage to get in the swag mention at the very end in these kinds of presentations. I watched the video. Did not get shirt. Was disappointed.

TheWimpossible

I don't quite get the point about scope and "there has to be a dot in there" when you use bidirectional binding... Does that mean I should always define my scope members like

$scope.member = { attribute1: value };

and refer them in the html via

SaschaKleiber