e-oz

<?php
namespace Sypex\Geo;

/***************************************************************************\
| Sypex Geo                  version 1.0.0 beta 2                           |
| (c)2006 zapimir            zapimir@zapimir.net       http://sypex.net/    |
| (c)2006 BINOVATOR          info@sypex.net                                 |
|---------------------------------------------------------------------------|
|     created: 2006.10.17 18:33              modified: 2006.10.26 22:07     |
|---------------------------------------------------------------------------|

e-oz

// Host where all  mp3 files are located
var musicHost = 'http://player.tupi.ca/webinar/music/';

// List of available files
var files = [
	'Chris_de_Burgh_-_The_Snows_Of_New_York.mp3',
	'Metallica_-_Nothing_Else_Matters.mp3',
	'R.E.M._-_Losing_My_Religion.mp3',
	'Scooter_-_How_much_is_the_fish.mp3',
	'Skrillex_-_Scary_Monsters_and_Nice_Sprites.mp3'

e-oz

Author of quoted text: Colin Johnsun
Original: http://www.johnpapa.net/structuring-an-angular-project/#comment-142821

I agree with Joel, I found that dividing by functional area made more sense to my workflow.
I tend to work on a particular function in my application and having all related code in the same folder made it easy and quicker to locate them. In my Angular apps, I don’t have separate controller and views folders. Instead, I would have a folder for login, sales, shipping, etc which would contain my related controllers and views. Although I do group by types for services and directives.
Ward mentions about cross cutting concerns. For me, Angular feels more like an MVVM framework than MVC and in my apps, the controllers are the view-models. In the “Shipping” and “Sales” module example, I would have a shipping controller and a sales controllers for each of the respective modules. If the notion of “customer” is roughly the same in both modules then this notion of customer can be abstracted out i

e-oz

  for user in $(cut -f1 -d: /etc/passwd); do echo $user; crontab -u $user -l; done

e-oz

by.addLocator('link',
      /**
       * Find <a> element by href attribute
       * @param {string} href
       * @param {Node} [parentElement=]
       * @returns {Array.<Node>}
       */
      function (href, parentElement) {
        parentElement = parentElement || document;
        var links = parentElement.querySelectorAll('a');

e-oz

by.addLocator('attr',
      /**
       * Find element(s), where attribute = value
       * @param {string} attr
       * @param {string} value
       * @param {Element} [parentElement=]
       * @returns {Array.<Element>}
       */
      function (attr, value, parentElement) {
        parentElement = parentElement || document;

e-oz

       /**
       * Click option[index] of select element
       * @param select
       * @param index
       * @returns {protractor.promise}
       */
        function clickOption(select, index) {
        var deferred = protractor.promise.defer();
        select.click().then(function () {
          var options = select.all(by.css('option'));

e-oz

Just because Twitter is incommodious for discussions. Started from this tweet: https://twitter.com/djsmith42/status/571566878562230272

e-oz

'use strict';

// @ngInject
function exmpNavigation($state) {
  return {
    restrict: '',
    templateUrl: 'components/exmpNavigation/template.html',
    controllerAs: 'cNav',
    controller: function () {
      this.go = function (route) {

e-oz

'use strict';

// @ngInject
function UserEventsLog($resource, Config, Token) {
  return $resource(Config.apiUrl + '/user_events/:token', {token: Token.get()}, {
    count: {
      method: 'GET',
      url: Config.apiUrl + '/user_events/count/:token',
      isArray: false,
      transformResponse: function (data) {