askn

Modified Preorder Tree Traversal

Hierarchical data metrics that allows fast read operations on tree like structures.

Based on Left and Right fields that are set during tree traversal. When entered into node value is set to it's Left, when exiting node value is set to it's Right.

Sample implementation

MarZab

<template>
  <div
    :tabindex="searchable ? -1 : tabindex"
    :class="[isOpen?'active':'', disabled?'disabled':'', size && size !== 'default'? 'multiselect-'+size : '' ]"
    @focus="activate()"
    @keydown.self.down.prevent="pointerForward()"
    @keydown.self.up.prevent="pointerBackward()"
    @keydown.enter.tab.stop.self="addPointerElement($event)"
    @keyup.esc="deactivate()"
    class="multiselect">

ryanflorence

<Route location="history" handler={require('../handlers/app')}>
  <Route name="search" path="/search" handler={require('../handlers/search')} />
  <Route name="profile" path="/:userName" handler={require('../handler/profile')} />
</Route>

krisselden

{{#each fruits}}
{{this}}
{{/each}}

{{draggable-list values=fruits}}

machty

router.js Architecture

Let this serve as a guide for anyone who'd like to dig into router.js's internals, understand what's going on, and hopefully contribute!

Scope of router.js (et al)

router.js is most popularly known as the routing microlib used by the Ember.js Router, though other folk have been known to use it beyond Ember, including some Angular folk who weren't satisfied with

achakravarty

var App = Ember.Application.create();

App.Router.map(function(){
	this.resource('user');
});

App.UserController = Ember.ObjectController.extend(Ember.Evented, {
	actions: {
		submit: function(){
			var validation = {isValid: false};

machty

Update 6/14/13

• see https://gist.github.com/machty/5723945 for the latest API (unlikely to change from now on)
• latest Ember build: https://machty.s3.amazonaws.com/ember/ember-async-routing-10.js

Router Facelift Examples

Guide to latest API enhancements router.js PR Ember PR

evilmarty

In my journey in figuring out the Ember pattern, this is my attempt at trying to create an Ember-only autocomplete field. There were a few outcomes I wanted out of this, a part from being the Ember-way:

• Work with any data source
• Easily templatable results
• Use only Ember constructs

All are welcome to use this, I'm just after feedback at this point.

hatefulcrawdad

/* The Grid ---------------------- */
.lt-ie9 .row { width: 940px; max-width: 100%; min-width: 768px; margin: 0 auto; }
.lt-ie9 .row .row { width: auto; max-width: none; min-width: 0; margin: 0 -15px; }
.lt-ie9 .row.large-collapse .column, 
.lt-ie9 .row.large-collapse .columns { padding: 0; }
.lt-ie9 .row .row { width: auto; max-width: none; min-width: 0; margin: 0 -15px; }
.lt-ie9 .row .row.large-collapse { margin: 0; }

.lt-ie9 .column, .lt-ie9 .columns { float: left; min-height: 1px; padding: 0 15px; position: relative; }
.lt-ie9 .column.large-centered, .columns.large-centered { float: none; margin: 0 auto; }

bubba-h57

<?php

namespace H57\Util;

class Serializor {
	
	/**
	 * Converts the Doctrine Entity into a JSON Representation
	 * 
	 * @param object $object The Object (Typically a Doctrine Entity) to convert to an array