Geoffrey Donaldson geoffreyd

@publickeating So after all that, did you not read the posts, or just choose to ignore the actual issues that where brought up?

did you have something to say about how we'll handle useStaticLayout with the 2 different view types? I guess,will this even be an issue? The view could detect if a template has been given, and set useStaticLayout: NO.

How about the fact that template views go against the design principals allowing an interface builder?

Also yes, the Ember guys have left us, but unfortunately their legacy hasn't. The very fact we have 'core_view' (plus the whole 'modularising' of SC) was from their first attempt at making SC 2, before choosing to start anew. What Erich is saying, is many of these changes where made without regard for performance of large apps. This is something that we need to take into consideration for each and every change we make. While you might not have a vision for where you want SC to go, many of us do. It's why most have chosen SC, and that vision is a framework tha

Keybase proof

I hereby claim:

I am geoffreyd on github.
I am geoffreyd (https://keybase.io/geoffreyd) on keybase.
I have a public key whose fingerprint is 0452 62F1 55A0 1BD3 9641 673A 1CF9 1EC3 6307 8A1B

To claim this, I am signing this object:

	//Is this correct?
	SC.ImageView.design({
	// You don't need to have both a 'right' and a 'width', just one or the other
	layout: { top: 100, left: 840, rotate: 90, height: 150, width: 130 },
	value: static_url('resources/aly.JPG'),
	localize: NO,

	mouseDown: function(evt) {
	// This will hide the current image when clicked
	this.set('isVisible', YES) ;

	App = SC.Application.create(
	/** @scope Chase.prototype */ {

	NAMESPACE: 'App',
	VERSION: '0.1.0',

	// This is your application store. You will use this store to access all
	// of your model data. You can also set a data source on this store to
	// connect to a backend server. The default setup below connects the store
	// to any fixtures you define.

	App = SC.Application.create(
	/** @scope Chase.prototype */ {

	NAMESPACE: 'App',
	VERSION: '0.1.0',

	// This is your application store. You will use this store to access all
	// of your model data. You can also set a data source on this store to
	// connect to a backend server. The default setup below connects the store
	// to any fixtures you define.

	app.get('/move/:from/:to', function(req, res) {
	console.log("Move");
	// Define the 'board' parameter here.
	board.load(function(board) {
	from = req.params.from
	to = req.params.to
	// The scope of `this is far too finicky, it's always better to
	// try another option if you can. In this case
	res.send({removed: board.move(from, to)})
	});

	Pharos360.labelsController = SC.ArrayController.create(
	/** @scope Pharos360.labels.prototype */ {

	// TODO: Add your own code here.

	}) ;

	Pharos360.Course = SC.Record.extend(
	/** @scope Pharos360.Course.prototype */ {

	primaryKey: 'number',

	number: SC.Record.attr(Number),
	title: SC.Record.attr(String),
	credit_hours: SC.Record.attr(String),
	days: SC.Record.attr(String),
	start_time: SC.Record.attr(String),

	* About to connect() to commits.geoffreyd.com port 80 (#0)
	* Trying 184.72.47.54... connected
	* Connected to commits.geoffreyd.com (184.72.47.54) port 80 (#0)
	* Server auth using Basic with user 'XXXX'
	> POST /gitpost HTTP/1.1
	> Authorization: Basic XXXXXX
	> User-Agent: curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3
	> Host: commits.geoffreyd.com
	> Accept: /
	> Content-Type:application/json

	exports['git-commits'] = function(doc, req) {
	var newDoc = JSON.parse(req.body);
	newDoc.type = 'commit';
	if (req.uuid) {
	newDoc._id = req.uuid;
	} else {
	newDoc._id = "commit-"+Date.now()+newDoc.repository.url;
	}
	return [newDoc, '{"status":"ok"}'];
	}