polotek

This is a brain dump of my experience trying to get something going with Ember.js. My goal was to get to know the ins and outs of the framework by completing a pretty well defined task that I had lots of domain knowledge about. In this case reproducing a simple Yammer feed. As of this time, I have not been able to complete that task. So this is a subjective rundown of the things I think make it difficult to get a handle on Ember. NOTE: My comments are addressing the Ember team and giving suggestions on what they could do to improve the situation.

App setup

The new guides have pretty good explanation of the various parts of the framework; routers, models, templates, views. But it's not clear how they all get strapped together to make something that works. There are snippets of examples all over the place like:

App.Router.map(function() {
  match('/home').to('home');
});

ivanvanderbyl

App.AccountEditRoute = Ember.Route.extend({
  setupController: function(controller) {
    controller.set('content', this.get('currentUser'));
  }
});

iStefo

// include this code in your application, you don't need to call any initialization manually!

Ember.Application.initializer({
  name: "meta",

  initialize: function(container, application) {
    // helper function to get tag from dom
    var _getTag = function(tagname, property, value) {
      var tags = document.head.getElementsByTagName(tagname),
        tag,

machty

Query Param API Examples

• Search queries
• Sort: client-side, no refiring of model hook
• Sort: server-side, refire model hook
• Pagination + Sorting
• Boolean values. False value removes QP from URL
• Global query params on app route
• Opt-in to full transition via refresh()
• replaceUrl by changing controller QP property

stevenharman

# /config/initializers/sidekiq.rb

current_web_concurrency = Proc.new do
  web_concurrency = ENV['WEB_CONCURRENCY']
  web_concurrency ||= Puma.respond_to?
  (:cli_config) && Puma.cli_config.options.fetch(:max_threads)
  web_concurrency || 16
end

local_redis_url = Proc.new do

eliotsykes

require 'rails_helper'

RSpec.describe TodosController, :type => :controller do

  describe "GET #index" do
  #describe "POST #create" do
  #describe "GET #show" do
  #describe "PATCH #update" do (or PUT #update)
  #describe "DELETE #destroy" do
  #describe "GET #new" do

code0100fun

// app/controllers/sign-in.js
import Ember from 'ember';

export default Ember.Controller.extend({
  actions: {
    signIn(){
      this.set('errors', null);
      var params = { identification: this.get('email'), password: this.get('password') };
      // Redirects to index route on success (configurable in config/environment.js)
      this.get('session').authenticate('simple-auth-authenticator:oauth2-password-grant', params);

dodeja

<style media="screen" type="text/css">
  .t49-cta { max-width: 430px;  font-family: sans-serif; margin: 15px; }
  .t49-cta a { color: #0275d8; text-decoration: none; }
  .t49-cta .copy { padding: 15px; border-bottom: 1px solid #ccc; }
  .t49-cta .form { text-align: center;padding: 10px; border-top: 1px solid #efefef; background: #efefef; border-radius: 0 0 4px 4px; }
  .t49-cta h1 { margin: 0; font-size: 20px; font-weight: 300; color: #66afe9; }
  .t49-cta .tsearch { min-width: 300px; padding: 0.375rem 0.75rem; line-height: 1.5; color: #55595c; border: 1px solid #66afe9;
    font-size: 14px; font-weight: 300; color: black; border-radius: 5px 0 0 5px; border-right-width: 0;}
  .t49-cta .btn { z-index: 2; margin-left: -4px;display: inline-block; background: white; border: 1px solid #0275d8;
    color: #0275d8; font-size: 14px; font-weight: 300; border-radius: 0 5px 5px 0;  user-select: none; padding: 0.375rem 1rem;

bmhatfield

# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

# Add the following to your shell init to set up gpg-agent automatically for every shell
if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
    source ~/.gnupg/.gpg-agent-info
    export GPG_AGENT_INFO
else

rondy

FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.

---

Effective Engineer - Notes

• By Edmond Lau
• Highly Recommended 👍
• http://www.theeffectiveengineer.com/

What's an Effective Engineer?