Sean Roberts sean-roberts

## 0_reuse_code.js
// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

## background.html
<script>

var Constants = {
	saveURL: 'http://random/birthday/saveimage.php',
	w: 500,
	h: 500,
	x: 200,
	y: 200
};

## PwQyzm.markdown

      
              3 files
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                sean-roberts
                / PwQyzm.markdown
            
            
              Created
              February 16, 2015 01:53
            
              
                PwQyzm
              
          
    PwQyzm

A Pen by sean-roberts on CodePen.
License.

  
## SelfInvokingFunctionWrapper.js
//version without passing in parameters that are not available in the function scope
;(function(){

  //code here

  //why the leading semi colon?
  // this is a safe way to keep from having conflicts with other code that uses the same
  // self invoking functions but left off the colon

})();

## WrapperObject.js
//start with a string literal
var a = "Hello, World";

//add a new property to that string
a.dateCreated = "6-4-2013";

//try to access that property
var b = a.dateCreated;

//b is still undefined

## NestedFunctionScope.js
foo(1);

function foo(a){
    var b = 2;

    bar(3);

    function bar(c){
        //all parent variables are visible and editable from here
        console.log(a);

## gist:6546754
/*
Notes from Eric Elliott's talk at the fluent conference
JavaScript has FREEDOM.

In classical inheritance you have tight coupling brought on by the parent-child relationship. This is good in some areas but as the project grows, making changes to the parent that ripple through the descendants can be a big burden and error/bug prone. Thus, the need for duplication by necessity. This is the situation where you have a class that does almost everything you want but it needs to do something a little differently so you create a very identical class for your new need. This is caused by the gorilla banana problem. Where you want a banana but what you got was a gorilla holding the banana and the entire jungle. The problem with object-oriented languages is they've got all this implicit environment that they carry around with them.

JavaScript has inheritance that does not have these problems.

"Program to an interface, not an implementation."
"Favor object composition over class inheritance."

## ObjectCreation.js
/*
    The different ways to create an object
*/


/*
    Example object needs to have this heirachy


## PublishSubscribeImpl.js
// test gist http://jsfiddle.net/fJPkr/1/

var handler = {};
(function(h){
    //holds the topics
    var topics = {},
        subUid = 0;

    h.publish = function(topic, args){
        //only publish topics that were subscribed to

## FunctionParametersAndArgs.js

//this foo function is really saying,
//"Hey, I am expecting about 3 arguments but give me what you can"
function foo(a, b, c){
  console.log(a,b,c);
}

//lets ask foo to take more and less parameters than expected

foo("anArg"); // logs in console => anArg undefined undefined
	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console
	<script>

	var Constants = {
	saveURL: 'http://random/birthday/saveimage.php',
	w: 500,
	h: 500,
	x: 200,
	y: 200
	};
	//version without passing in parameters that are not available in the function scope
	;(function(){

	//code here

	//why the leading semi colon?
	// this is a safe way to keep from having conflicts with other code that uses the same
	// self invoking functions but left off the colon

	})();
	//start with a string literal
	var a = "Hello, World";

	//add a new property to that string
	a.dateCreated = "6-4-2013";

	//try to access that property
	var b = a.dateCreated;

	//b is still undefined
	foo(1);

	function foo(a){
	var b = 2;

	bar(3);

	function bar(c){
	//all parent variables are visible and editable from here
	console.log(a);
	/*
	Notes from Eric Elliott's talk at the fluent conference
	JavaScript has FREEDOM.

	In classical inheritance you have tight coupling brought on by the parent-child relationship. This is good in some areas but as the project grows, making changes to the parent that ripple through the descendants can be a big burden and error/bug prone. Thus, the need for duplication by necessity. This is the situation where you have a class that does almost everything you want but it needs to do something a little differently so you create a very identical class for your new need. This is caused by the gorilla banana problem. Where you want a banana but what you got was a gorilla holding the banana and the entire jungle. The problem with object-oriented languages is they've got all this implicit environment that they carry around with them.

	JavaScript has inheritance that does not have these problems.

	"Program to an interface, not an implementation."
	"Favor object composition over class inheritance."
	/*
	The different ways to create an object
	*/




	/*
	Example object needs to have this heirachy
	// test gist http://jsfiddle.net/fJPkr/1/

	var handler = {};
	(function(h){
	//holds the topics
	var topics = {},
	subUid = 0;

	h.publish = function(topic, args){
	//only publish topics that were subscribed to

	//this foo function is really saying,
	//"Hey, I am expecting about 3 arguments but give me what you can"
	function foo(a, b, c){
	console.log(a,b,c);
	}

	//lets ask foo to take more and less parameters than expected

	foo("anArg"); // logs in console => anArg undefined undefined