kbingham

#!/bin/sh

set -e
#set -x

CONFIGFS="/sys/kernel/config"
GADGET="$CONFIGFS/usb_gadget"
VID="0x0525"
PID="0xa4a2"
SERIAL="0123456789"

Thundernerd

#if UNITY_EDITOR
using System;
using System.Reflection;
using UnityEditor;
using UnityEngine;

public static class Docker
{

    #region Reflection Types

stramit

using System;
using System.Collections.Generic;
using UnityEngine.Events;

// interface you implement in your MB to receive events
public interface ICustomHandler : IEventSystemHandler
{
	void OnCustomCode(CustomEventData eventData);
}

zostay

None of the workflow examples given in the Google Authentication OAuth2 documentation 
(https://developers.google.com/accounts/docs/OAuth2) handle what's needed for Pebble. I 
basically had to mix the needs of a client-side application with an offline web application 
to get what's needed and work within the restrictions of the Pebble JS toolkit.

The steps are as follows:

1. Setup a Client ID for Web Application on the Google Developer Console
2. On the configuration web pages, with SSL:
   * In the configuration page, use JavaScript to retrieve a authorization code, which 

yorkxin

Avoid jQuery When Possible

jQuery does good jobs when you're dealing with browser compatibility. But we're living in an age that fewer and fewer people use old-school browsers such as IE <= 7. With the growing of DOM APIs in modern browsers (including IE 8), most functions that jQuery provides are built-in natively.

When targeting only modern browsers, it is better to avoid using jQuery's backward-compatible features. Instead, use the native DOM API, which will make your web page run much faster than you might think (native C / C++ implementaion v.s. JavaScript).

If you're making a web page for iOS (e.g. UIWebView), you should use native DOM APIs because mobile Safari is not that old-school web browser; it supports lots of native DOM APIs.

If you're making a Chrome Extension, you should always use native APIs, not only because Chrome has almost the latest DOM APIs available, but this can also avoid performance issue and unnecessary memory occupation (each jQuery-driven extension needs a separate