I hereby claim:
- I am alexswensen on github.
- I am alexswensen (https://keybase.io/alexswensen) on keybase.
- I have a public key ASDisJ_B5nXGtEhH1vVm54yqch1aNtdsZ8OhNOhvSbNJJAo
To claim this, I am signing this object:
<ion-slide-box class="has-header" active-slide="activeSlide"> | |
<ion-slide ng-repeat="image in images"> | |
<ion-scroll direction="xy" scrollbar-x="false" scrollbar-y="false" | |
zooming="true" min-zoom="{{ zoomMin }}" style="width: 100%; height: 100%" | |
delegate-handle="scrollHandle{{$index}}" on-scroll="updateSlideStatus(activeSlide)" | |
on-release="updateSlideStatus(activeSlide)"> | |
<!-- content here --> |
// sample: http://codepen.io/ktknest/full/LDljw/ | |
angular.module('app', []) | |
/** | |
* @ngdoc directive | |
* @name pinchZoom | |
* @restrict A | |
* @scope false | |
* | |
* @description |
I hereby claim:
To claim this, I am signing this object:
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
Installing Python 3.6.1 on Raspbian =================================
As of January 2017, Raspbian does not yet include the latest Python release, Python 3.6. This means we will have to build it ourselves, and here is how to do it.
Install the required build-tools (some might already be installed on your system).
$scope.scanCode = function () { // Scan code | |
$ionicLoading.show({ | |
template: '<ion-spinner></ion-spinner>' | |
}); | |
console.log("scanCode run"); | |
if ($scope.currentlyScanning === true) { | |
$ionicLoading.hide(); | |
return; | |
} | |
else if (ionic.Platform.platforms.indexOf("browser") !== -1) { |
{ | |
"window.autoDetectColorScheme": true, | |
"workbench.preferredDarkColorTheme": "One Dark Pro", | |
"workbench.iconTheme": "vscode-icons", | |
"git.autofetch": true, | |
"editor.bracketPairColorization.enabled": true, | |
"files.autoSave": "onFocusChange", | |
"[javascript]": { | |
"editor.defaultFormatter": "esbenp.prettier-vscode" | |
}, |
import fs from 'fs'; | |
import path from 'path'; | |
import matter from 'gray-matter'; | |
export default async () => { | |
const posts = await readMarkdownFiles(); | |
return { | |
data: { posts } | |
}; | |
}; |