Mocked login works again

src/Umbraco.Web.UI.Client/docs/src/TestDrivenDevFlow.md

@@ -19,7 +19,6 @@ To start working on the client files, and have them automaticly built and merged
 	grunt dev
 
 This will start a webserver on :8080 and tell karma to run tests every time a .js or .less file is changed. 
-
 After linting and tests have passed, all the client files are copied to umrbaco.web.ui/umbraco folder, so it also keeps the server project uptodate on any client changes. This should all happen in the background.
 
 ##Adding a new service
@@ -30,17 +29,53 @@ This ensures 3 things:
 - we test our services
 - we always have mocked data available, if you want to run the client without IIS
 
+
+
 ###Example: 
 We add a service for fetching macros from the database, the initial implementation should happen of this service should happen in `/src/common/resources/macro.resource.js`
 
-The macro.resource.js calls `$http` as normal, but no server implementation should be needed at this point. 
+The macro.resource.js calls `$http` as normal, but no server implementation should be needed at this point.
 
 Next, we describe how the rest service should return data, this is done in /common/mocks/umbraco.httpbackend.js, where we can define what data a certain url
 would return. 
 
---- in progress ---
-
-
+So in the case of getting tree items we define:
+
+	$httpBackend
+		.whenGET( urlRegex('/umbraco/UmbracoTrees/ApplicationTreeApi/GetApplicationTrees') )
+		.respond(returnApplicationTrees);
+
+The `returnApplicationTrees` function then looks like this: 
+
+	function returnApplicationTrees(status, data, headers){
+		var app = getParameterByName(data, "application");
+		var tree = _backendData.tree.getApplication(app);
+		return [200, tree, null];
+	}
+
+It returns an array of 3 items, the http status code, the expected data, and finally it can return a collection of http headers.
+
+	_backendData.tree.getApplication(app);
+
+Refers to a helper method in `umbraco.httpbackend.helper.js` which contains all the helper methods we 
+use to return static json. 
+
+###In short
+So to add a service, which requires data from the server we should:
+
+- add the .service.js as normal
+- add the .resource.js as normal
+- call $http as normal
+- define the response data in umbraco.httpbackend.helper.js
+- define the url in umbraco.httpbackend.js
+
+###ServerVariables
+There is a static servervariables file in /mocks which describes the urls used by the rest service, this is currently needed as we dont have this set as a angular service, and no real conventions for these urls yet. Longer-term it would be great to have a urlBuilder which could do
+
+	urlService.url("contentTypes", "GetAllowedChildren");
+	//would return /<umbracodir>/<apibaseDir>/contentyTypes/getAllowedChildren
+
+But for now, they are set in the servervariables file.