jamesarosen

import Ember from 'ember';

export default Ember.Component.extend({
  classNames: [ 'delete-blog' ],
  
  sudoDeferred: null,
  isDone: false,
  isWorking: false,
  message: null,
  

jamesarosen

import Ember from 'ember';

export default Ember.Controller.extend({
  appName: 'Ember Twiddle'
});

jamesarosen

import Ember from 'ember';

export default Ember.Controller.extend({
  appName: 'Ember Twiddle'
});

jamesarosen

Impetus

I have several components that have complex flows. For example, a "deploy this code" button. It might have the following flow:

1. if the user is typing, the button is hidden
2. after the user stops typing, the button appears, is disabled, and reads "Saving..."
3. after the code is saved, the button is enabled and reads "Test & Deploy"
4. after the user clicks the button, it is disabled and reads "Testing..."
5. if the tests fail, the button remains disabled and reads "Tests Failed"
6. if the tests pass, the button remains disabled and reads "Deploying..."

jamesarosen

I have a form with three fields: Foo, Bar, Baz. Bar is really sensitive, so if the user changes it, I want to show a confirmation modal when the user tries to submit the form (but not until then). Currently, we have the is-bar-changed and show-modal logic in the containing form. I'd prefer to move it down into a component:edit-bar. But I can't figure out a good way to model that component having an opportunity to pause the parent form's submission, then continue or abort asynchronously.

Pass Down Hook Registry

One option would be for the form to yield some sort of hook registry:

jamesarosen

I don't have a Grand Vision for (S)CSS, but I do have some ideas.

Cohesion & Coupling

In JavaScript (and any other "programming language"), we value cohesion and eschew coupling. To value cohesion is to say that all of the foo-related things are in the Foo component or the app/pods/foo pod or the lib/foo addon. Like things are together. To eschew coupling is to say that two unrelated things should not need to know about one another. Unlike things don't rely on one another. Further reading on Cohesion & Coupling:

• http://courses.cs.washington.edu/courses/cse403/96sp/coupling-cohesion.html (my favorite reference on the topic)
• http://enterprisecraftsmanship.com/2015/09/02/cohesion-coupling-difference/ (good visuals)
• http://c2.com/cgi/wiki?CouplingAndCohesion
• https://en.wikipedia.org/wiki/Connascence_(computer_programming) (connascense is closely related to cohesion)

jamesarosen

import Ember from 'ember';

export default Ember.Controller.extend({
  appName: 'Ember Twiddle'
});

jamesarosen

import Ember from 'ember';

export default Ember.Component.extend({
  tagName: 'section',
  classNames: [ 'i18n-demo' ],
  
  i18n: Ember.inject.service(),
  beenClicked: false,
  text: Ember.computed('i18n.locale', function() 
{

jamesarosen

After my recent move, I've been sorting through old papers. I just found this page of notes I had prepared before meeting @wycats and @tomdale for lunch to discuss SproutCore vs Backbone. It's undated, but from around March 2011.

I remember very vividly the passion they showed over that meal. They knew they had a long road ahead of them to convince the web-developer community of the value of this framework and that many substantial changes would be needed. But they had a vision and a group of people that were willing to give them a chance.

• why #getEach instead of #pluck?

jamesarosen

import Ember from 'ember';

export default Ember.Controller.extend({
  appName: 'Ember Twiddle'
});