regarding #8 (dependency injection stuff), I'd recommend using this pattern to handle it. if you do it this way there should be no issues with minification, and better still, you're fully modularizing everything and its all self contained so you can reuse your whole module in another angular app if you wanted to.
// first register your module as a new module in angular var MyModule = angular.module('MyModule',[outside module dependencies injected here]);
// next register your controller as a new controller in your module MyModule.controller('MyController', function($scope, $http, $timeout) { // my controller code here });
Comment
regarding #8 (dependency injection stuff), I'd recommend using this pattern to handle it. if you do it this way there should be no issues with minification, and better still, you're fully modularizing everything and its all self contained so you can reuse your whole module in another angular app if you wanted to.
// first register your module as a new module in angular
var MyModule = angular.module('MyModule',[outside module dependencies injected here]);
// next register your controller as a new controller in your module
MyModule.controller('MyController', function($scope, $http, $timeout) {
// my controller code here
});