scottmessinger

import SortableListMixin from '../mixins/sortable-list';
import Part from '../models/part';
import Section from '../models/section';

var PartsController = Ember.ArrayController.extend(SortableListMixin, {
    init: function(){
        this._super()
        // ISSUE #1  - probably unrelated the es6 change.
        // Shouldn't the content be set automatically to an array?
        if (Ember.isNone(this.get('content'))){

scottmessinger

Ember does a bunch of useful, powerful, magical things that makes life easy. However, I find myself often a loss to understand how the magic works or how to hook into it. I think I struggle most to understand how & when things are instantiated, how they magically know of each other (e.g. the app knows all it's models & controllers), and how to instantiate things manually and give them access to all the other classes. Here are some examples:

• If I create an instance of a controller, how do I make sure it has access to the app containers?
• In Ember-CLI, how does Ember know about all the models/controllers/etc I create? When I write export default PostController, how does Ember register that as a controller and add it to the container?
• In Ember-CLI, filenames & folder names make a difference. If files are named something unexpected, the documentation writes that they need to be imported automiatcally. Where would such an import statement go? What is the code path that the abnormally named class has to ski

scottmessinger

type == "routine"

scottmessinger

<!--
template: planbook.hbs 
-->

{{render 'dates'}}


<!--
template: dates.hbs
controller: see DatesController below

scottmessinger

App.PlanbookDate = Ember.Model.extend({
  
  /**
   *  Computed Property
   * This property returns a routine. If the routine is pristine,
   * it creates a routine then adds parts from the routine template to it.
   * 
   * If the routine is not pristine, it just returns the routine.
   * 
   */

scottmessinger

class OldNode

  def lesson
    @lesson ||= Lesson.find(id)
  end
  
  def verify_migration
    self.verify_field_names
    self.verify_sections
  end

scottmessinger

/**
 *  [SCATTER](http://nvd3.org/examples/scatter.html)
 */
 
[
  {
    "key": "Group 0",
    "values": [
      {
        "x": 0.6396293678966859,

scottmessinger

// SearchController
export default Ember.Controller.extend({
  queryParams: ['query']
})

// SearchController template
{{x-search query=query}}

// X-Search component
export default Ember.Component.extend({

scottmessinger

Suggested Plan to migrate from AR to ES in our Rails app

Clean up Queries

• Change the specs and the queries to move filters from filter to query.filtered.filter
• Move {term: {budget_lea_id: budget_lea_id} from query to query.filtered.filter

Remove JBuilder

• Create PayloadBuilder library to build payloads
• Convert JBuilder code to PayloadBuilder library

scottmessinger

# Usage: Setup
module A
  extend Transproc::Registry
  def self.hi(message)
    h[:a_message] = message
  end
end

module B
  extend Transproc::Registry