cerebrl

/** ****************************************
 * Utility file
 * mixin.js
 * @returns [object]
 */
function mixinFactory() {
	var len = arguments.length,
		i = 0,
		finalObj = {};
	

cerebrl

/** ****************************************
 * Constructor for say hi feature.
 * @constructor SayHiConstructor
 * @returns {object}
 */
function SayHiConstructor() {
	this.greeting = "Basic module says, 'hallo'!"
}
SayHi.prototype.sayHi = function sayHi() {
	this.writeToConsole());

cerebrl

/** ****************************************
 * Module for say hi feature
 * @module sayHiFactory
 * @returns {object}
 */
function sayHiFactory() {
	var greeting = "Basic module says, 'hallo'!"
  
	function prvtWriteToConsole() {
		console.log(greeting);

cerebrl

// Sample object
var mySampleData = {
    foo: {
        bar: [
            1,
            2,
            {
                baz: "hello",
                wut: 2,
                hi: [7, 8, 9]

cerebrl

General JavaScript

Books

• Eloquent JavaScript
• Effective JavaScript
• JavaScript: The Good Parts
• Programming JavaScript Applications
• Learning JavaScript Design Patterns
• You Don't Know JavaScript

cerebrl

/** ****************************************
 * Utility file
 * mixin.js
 * @returns [object]
 */
function mixinFactory() {
	var len = arguments.length,
		i = 0,
		finalObj = {};
	

cerebrl

Front-End Processes, Workflows and Standards

1. Definition: The front-end consists of any code that is run on the client (browser): HTML, CSS and JavaScript.
2. Agnostic and independent front-end code is priority. Front-end code should not represent server/back-end architecture.
3. Modularity and encapsulation is vital to increase reusability and following the DRY philosophy.
4. The MVC philosophy (when developing web-applications) should be closely followed, but exact replication may be unnecessary. The structure goes as follows:
   • Model: Models do not technically exist in the client (unless using client-sided storage (localStorage, et cetera), but act more as temporary data stores between getting and setting data with the server. So, this temporary data store will be considered and called a Service. Data should always exist as native JSON either as objects or arrays.
   • View: Views should be pure HTML containing virtually no logic. Element attributes (data-, classes, ids, ng-model,

cerebrl

AngularJS localStorage

This was nabbed from DailyJS

There are examples of apps that use localStorage on the AngularJS blog. One that I downloaded and picked apart was FoodMe by Igor Minar. In FoodMe, Igor creates a localStorage service which basically just wraps window.localStorage so it can be loaded with dependency injection. The $scope is then watched, and a string version of a given record is dumped into localStorage using JSON.stringify:

foodMeApp.factory('customer', function($rootScope, localStorage) {
	var LOCAL_STORAGE_ID = 'fmCustomer';
	var customerString = localStorage[LOCAL_STORAGE_ID];

cerebrl

alias gitA="git add -A && git status "
alias gitS="git status "
alias gitPl="git pull "
alias gitCm="git commit -m "
alias gitACm="gitA && gitCm "
alias gitPPM="git pull && git push origin master "
alias gitPB="git push origin "
alias gitPg="git checkout gh-pages && git push origin gh-pages && git checkout master && git branch -d gh-pages"
alias gitCkM="git checkout master "
alias gitStPlPhi="git subtree pull --prefix=phi git@github.com:cerebralideas/phi.git "

cerebrl

{
    // --------------------------------------------------------------------
    // JSHint Configuration, Strict Edition
    // --------------------------------------------------------------------
    //
    // This is a options template for [JSHint][1], using [JSHint example][2]
    // and [Ory Band's example][3] as basis and setting config values to
    // be most strict:
    //
    // * set all enforcing options to true