jshirley

  views : {
    GoalListView : {
        type      : NS.GoalListView,
        requires  : [ 'Person', 'CategoryList', 'GoalList', 'NoteList' ],
        preserve  : true
    }
  },

  showGoalView : function(req, res, next) {
    this.handleView('GoalListView', req, res, next);

paulirish

Open Conference Expectations

This document lays out some baseline expectations between conference speakers and conference presenters. The general goal is to maximize the value the conference provides to its attendees and community and to let speakers know what they might reasonably expect from a conference.

We believe that all speakers should reasonably expect these things, not just speakers who are known to draw large crowds, because no one is a rockstar but more people should have the chance to be one. We believe that conferences are better -- and, dare we say, more diverse -- when the people speaking are not just the people who can afford to get themselves there, either because their company paid or they foot the bill themselves. Basically, this isn't a rock show rider, it's some ideas that should help get the voices of lesser known folks heard.

These expectations should serve as a starting point for discussion between speaker and organizer. They are not a list of demands; they are a list of rea

juandopazo

I think the goal should be to replace Express with Y.App. Express does:

• Routing
• Redirection
• Environment configuration
• View templating and rendering
• Everything Connect does

Routing and redirection are very much in the scope of Y.Router/Y.App. Environment configuration is in the scope of YUI. View templating and rendering are also covered. Rendering of static files, middleware, logging, caching, cookies, compression, etc are all covered by Connect. So... Shouldn't the goal be to make Y.App work nicely with Connect?

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

voidfiles

How you can create a responsive grid system using YUI3 grids and SASS

This is a quick rundown of how and why we use YUI3 grids at App.net

As far as I can tell there are three types of CSS grids: a static-width pre-defined grid, a flexible-width pre-defined grid, and a generative grid. In the first two grids (pre-defined width), you basically decide how many columns you have across the screen, and then create blocks in any multiple of those. This pattern often looks like "span-4", "span-6", "pull-10", "push-5", etc. You find this style in popular frameworks like Bootstrap and Blueprint.

The third way, the generative/recursive grid system, doesn't seem to be as popular as the others. I am not entirely sure why, because the generative grid can pack more punch in less lines. In this vein is there is OOCSS and YUI3 CSS Grids.

domenic

This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.

You're Missing the Point of Promises

Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:

getTweetsFor("domenic", function (err, results) {
 // the rest of your code goes here.

balupton

Debugging & Profiling Node.js - Moved! Click here to be redirected to the new location.

davglass

Dav's Yeti Cluster

Direct Hardware

• Ubuntu VM Host
  • Dual Core i5@2.80GHz
  • 16 GB Ram
• 1TB HDD (for OS)

caridy

var microtime = require('microtime'),
    i,
    t,
    obj,
    max = 10000000;

function run1(obj) {
    t = microtime.now();
    for (i = 0; i < max; i += 1) {
        if (obj.foo) obj.foo();

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');
});