Tyler Gaw tylergaw

Since the introduction of HTMLBars in Ember, you've been able set attribute on elements in templates using boolean properties.

Here's the example from their docs located at http://guides.emberjs.com/v1.12.0/templates/binding-element-attributes/

Template:

<input type="checkbox" disabled={{isAdministrator}}>

HTML Output:

Dong some learnin' about the osacompile command for using JS to write OS X apps/applets/automations etc. If you're on Yosemite (or greater):

Download this here JavaScript file https://www.dropbox.com/s/r6bcw0xjykfqb8a/mycool.js?dl=0
use yer handy terminal and run: osacompile -l JavaScript -s -o MyCool.app mycool.js
That will create the "MyCool" App.
Double click that dude and you should see a little mini app

Safari CORs

This example works in Chrome and Firefox but will fail in Safari http://jsfiddle.net/9qxs5gdf/

Safari sends the origin header along with the first OPTIONS request. I'm wondering if the Dribbble API does not allow that header?

From Safari: Access-Control-Request-Headers accept, authorization, origin

Saw a similar issue here:

Jribbble Shots Example 001 ('-' * 26)

A Pen by Tyler Gaw on CodePen.

License.

I'm attempting to make CORs requests to the Dribbble API v1. I can do so using a standard XMLHttpRequest, but cannot using jQuery's $.ajax.

I'm trying to determine if I'm just doing something wrong with the jQuery request, if jQuery is doing something wrong, or if the Dribbble server is missing some bit of CORs configuration.

Here is a working example showing two different CORs requests: http://jsfiddle.net/thegaw/pec38u18/

One thing that is sticking out to me is that the jQuery request is setting the following header:

Access-Control-Request-Headers:accept, authorization

In the Ember cli docs it states that you can specify the --type option when generating a controller.

From the docs at http://www.ember-cli.com/#detailed-list-of-blueprints-and-their-use

Controller

Generates a Controller of a given name and type, with accompanying test.
Options
- Type
Basic

I was trying to use nodegit and was running into trouble. I followed the install instructions on the README and then tried the examples there, but was getting errors for anything beyond requiring the package.

For now it seems you can't use the version of nodegit that is published to npm.

npm install nodegit

That will install version 0.1.4. Which seems to not work. Here's an example of what would happen.

I'm trying to enable source maps for Sass on my site http://tylergaw.com.

If you go there and look at:

developer tools > sources > tylergaw.com > css > scss

you'll see modules and partials. Both of those directories have all the file names for the source files. If you click on any of them nothing will load. And if you hop over to the console you'll see that they a 404. That's because they do not exist on the server. That's my issue.

I'm using Jekyll to generate my site. When jekyll builds it copies the scss dir from src to public (my jekyll destination dir), but strips out all subdirectories. In this case modules and partials. For some reason it leaves the .scss file in there.

	#!/bin/sh

	git rev-parse 2>/dev/null

	if [[ $? != 0 ]]
	then
	echo "Not a git repo"
	return
	fi

	Replace YOURCODEHERE with your code:
	http://www.ticketweb.com/t3/sale/SaleEventDetailSubmit?dispatch=proceed&eventId=6580715&pl=webconcerts&view=list&promoCode=YOURCODEHERE&org.apache.struts.taglib.html.CANCEL=Apply+Access+Code