Angular.js - Revision history

Adamcolton: /* What I don't Get */

2014-08-11T14:37:32Z

What I don't Get

← Older revision		Revision as of 14:37, 11 August 2014
Line 100:		Line 100:

	== What I don't Get ==		== What I don't Get ==
	It seems that the tight coupling of logic and display is bad. Particularly embedding a turing-complete DSL in element attributes.		It seems that the tight coupling of logic and display is bad. Particularly embedding a turing-complete DSL in element attributes ie. angular expressions.

	Binding is a neat trick, but is it really useful? Often I don't want the display tightly coupled to the model so that I can perform some layer of processing on it.		Binding is a neat trick, but is it really useful? Often I don't want the display tightly coupled to the model so that I can perform some layer of processing on it.

2014-08-11T14:26:46Z

What I don't Get

← Older revision		Revision as of 14:26, 11 August 2014
Line 103:		Line 103:

	Binding is a neat trick, but is it really useful? Often I don't want the display tightly coupled to the model so that I can perform some layer of processing on it.		Binding is a neat trick, but is it really useful? Often I don't want the display tightly coupled to the model so that I can perform some layer of processing on it.

			There was a great example of the non-intuitive state that Angular leaves the user in:
			setTimeout(function(){
			$scope.name="Bob";
			});
			This would be put in a controller somewhere, presumably the setup. But it will never appear to be called, the because the setTimeout happens "outside the Angular world", so we need to use .$apply

	[[Category:Code]]		[[Category:Code]]
	[[Category:Notes]]		[[Category:Notes]]

2014-08-11T14:02:49Z

Creating a controller

← Older revision		Revision as of 14:02, 11 August 2014
Line 27:		Line 27:
	app.controller(controllers);		app.controller(controllers);
	This works for directives too, but not filters.		This works for directives too, but not filters.

			The important thing is that a controller is just a function. When it's linked to some chunk of html, it binds $scope to the model.

	== Service ==		== Service ==

2014-08-11T13:15:41Z

What I don't Get

← Older revision		Revision as of 13:15, 11 August 2014
Line 98:		Line 98:

	== What I don't Get ==		== What I don't Get ==
	It seems that the tight coupling of logic and display is bad.		It seems that the tight coupling of logic and display is bad. Particularly embedding a turing-complete DSL in element attributes.

	Binding is a neat trick, but is it really useful? Often I don't want the display tightly coupled to the model so that I can perform some layer of processing on it.		Binding is a neat trick, but is it really useful? Often I don't want the display tightly coupled to the model so that I can perform some layer of processing on it.

2014-08-08T21:44:35Z

What I don't Get

← Older revision		Revision as of 21:44, 8 August 2014
Line 99:		Line 99:
	== What I don't Get ==		== What I don't Get ==
	It seems that the tight coupling of logic and display is bad.		It seems that the tight coupling of logic and display is bad.

			Binding is a neat trick, but is it really useful? Often I don't want the display tightly coupled to the model so that I can perform some layer of processing on it.

	[[Category:Code]]		[[Category:Code]]
	[[Category:Notes]]		[[Category:Notes]]

2014-08-08T21:43:04Z

← Older revision		Revision as of 21:43, 8 August 2014
Line 96:		Line 96:

	I still don't understand providers.		I still don't understand providers.

			== What I don't Get ==
			It seems that the tight coupling of logic and display is bad.

	[[Category:Code]]		[[Category:Code]]
	[[Category:Notes]]		[[Category:Notes]]

2014-03-22T01:01:39Z

Difference in Types

← Older revision		Revision as of 01:01, 22 March 2014
Line 93:		Line 93:

	module.factory( 'factoryName', funcFooBar );		module.factory( 'factoryName', funcFooBar );
	When inject, will return the result of funcFooBar.		When inject, will return the result of funcFooBar().

	I still don't understand providers.		I still don't understand providers.

2014-03-22T00:57:27Z

← Older revision		Revision as of 00:57, 22 March 2014
Line 87:		Line 87:
	* =: gets the object value		* =: gets the object value
	* &: parent scope, or..., method on parent scope, maybe?		* &: parent scope, or..., method on parent scope, maybe?

			== Difference in Types ==
			module.service( 'serviceName', funcFooBar );
			When injected, will return new funcFooBar()

			module.factory( 'factoryName', funcFooBar );
			When inject, will return the result of funcFooBar.

			I still don't understand providers.

	[[Category:Code]]		[[Category:Code]]
	[[Category:Notes]]		[[Category:Notes]]

2014-03-19T02:18:28Z

Service

← Older revision		Revision as of 02:18, 19 March 2014
Line 29:		Line 29:

	== Service ==		== Service ==
			app.factory('ServiceName', function(){
	app.factory('ServiceName', function(){		return serviceData;
	return serviceData;		})
	})

	== Filter ==		== Filter ==

2014-03-19T01:53:21Z

Creating a controller

← Older revision		Revision as of 01:53, 19 March 2014
Line 26:		Line 26:
	}		}
	app.controller(controllers);		app.controller(controllers);
	This works for directives too.		This works for directives too, but not filters.

	== Service ==		== Service ==