This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<!--- coldfusion 8 version ---> | |
<cfcomponent> | |
<cffunction name="plupload" access="remote" returntype="struct" returnformat="json" output="false"> | |
<cfargument name="name" default="" /> | |
<cfscript> | |
var uploadDir = expandPath('../assets/'); | |
var uploadFile = uploadDir & arguments.NAME; | |
var response = {result = arguments.NAME, id = 0}; | |
var result = {}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 |