7.5-get-to-know-ember Scott Green

[scott6455]

Deliverables

A Issue on Github with

• [x] Things that look familar when looking at the projects
• [x] Questions about things you don't recognize

[scott6455]

//Questions and comments for Ember.js Intro//

• [ ] What is .gitkeep used for and when? Will the user input or information be what makes up the .gitkeep content?
• [ ] In the 'classes' folder the import command "import Ember from 'ember'" was used in each file. Why does it need to be repeated if one of the main purposes of Ember is to reduce repetition?
• [ ] In the macros screencast / video the properties "and", "or", and "alias" were used...did they come from JavaScript code or intialized by Ember.js programmers? They seem very clear, logical and really simple properties and I am curious why we don't see them more?
• [ ] How often is the logic not true or incorrect after a pass of Ember's wand of logical trimming? Is there a method to skip blocks of code or tell Ember to not do its "thing" to certain code and if so, what examples?

• [ ] Can you summerize or explain the following:

  -  .jshintrc
  -  firebase
  -  watchman
  -  emberfire.js (is this addon like a chrome extension?)
  -  

Similarities in the Code ==

• the boilerplate seemed familar;
• return (/\?/) <----- Do what?????
• there is a lot to process and work on...that's familiar

[rtablada]

@scott6455

the import syntax is part of ES6 to allow modularity and the ability to change out dependencies with minimum impact. If for instance we wanted to instead of using Ember, use something that had the same functions with slightly different behavior we could import Ember from 'other-vendor/ember'; and not change any other code

the .gitkeep files are there so that the folder structure is not lost when committing with git. In git empty folders are not tracked, so adding a blank .gitkeep is a standard way of having a place for future files.

the and, or and alias computed macros are Ember's way of implementing this type of logic while wrapping the existing KVO (Key Value Observer) change event system that exists in Ember. These concepts aren't new and we can use the && and || operators in plain javascript when using standard boolean expressions ie true && false.

There are occasional times where you will find Ember acting weird around data showing up differently. This is often an issue of your own making by passing around more complex data or relying on side-effects. Due to the layers of abstraction, there are ways to change the default auto wiring although I will have to say "there be dragons"

.jshintrc - sets up config for a project with JSHint (the linter that runs when we save a file and it checks for style and syntax errors)

Firebase - a simple to use Platform as a Service. This is essentially a quick and dirty database that we can access directly from the browser. It also performs real time communication via web sockets that makes things like web chat fairly easy.

watchman - this is a program by Facebook that is really good at checking for when files change without locking up the disc or using too much CPU