git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git
cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream
git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git
cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream
/* | |
Simple program to print out available wifi networks | |
Taken from http://stackoverflow.com/a/16752895/141084 | |
To build & run: | |
sudo apt-get install libiw-dev | |
gcc -liw test.c |
No, seriously, don't. You're probably reading this because you've asked what VPN service to use, and this is the answer.
Note: The content in this post does not apply to using VPN for their intended purpose; that is, as a virtual private (internal) network. It only applies to using it as a glorified proxy, which is what every third-party "VPN provider" does.
These instructions will not work on Chromebooks with an ARM processor. If you have an ARM processor then you cannot install Chromebrew to get git. You'll need to instead install crouton. Here are instructions that you can follow: https://github.com/macton/arch-linux-install-notes/tree/master/arm-chromebook-chroot
#Configuring Chromebook for Development
After a full Sunday of trial and error, and stepping through many semi-complete or dated blog posts explaining how to do this, I was able to get the Chromebook into developer mode, install git, Node.js, and NPM.
Here's what I did...
Esc-Refresh-Power
keys which will reboot the Chromebookint doubler(int x) { | |
return 2 * x; | |
} |
/** | |
* iLog : intelligent logger. | |
* Supports : .log(), .warn(), .error(), and .info() | |
* Configuring : | |
* Change iLogCfg to your fit. | |
* Supports color changes and enable/disable stack trace for each of the log functions | |
* Use : | |
* console.ilog('my comment'); | |
* -> my comment | |
* console.ilog(myVar1, myVar2, [more...]); |
Algorithms used for Cone* preprocess the mesh in some way, then split sequentially into 64-triangle clusters: | |
ConeBase: optimize mesh for transform cache | |
ConeSort: split mesh into large planar connected clusters, bin clusters into 6 buckets by cardinal axes, optimize each bucket for transform cache | |
ConeAcmr: optimize mesh for transform cache, split sequentially into variable length clusters that are relatively planar, sort clusters by avg normal | |
ConeCash: optimize mesh for transform cache, picking triangles that reduce ACMR but prioritizing those that keep current cluster planar | |
MaskBase: split sequentially into 64-triangle clusters, store a 64-bit conservative triangle mask for 6 frustums (cube faces) | |
ManyConeN: split sequentially into 64-triangle clusters, store N (up to 4) cones for each cluster and a cone id per triangle (2 bit) | |
Note that all Cone* solutions get significantly worse results with 128 or 256 triangle clusters; it doesn't matter much for Mask. | |
The biggest challenge with Cone* algorithms is t |
# Example video made by this script: https://twitter.com/erkaman2/status/990873258416361472 | |
ffmpeg \ | |
-y \ | |
-i vid1.mp4 \ | |
-i vid2.mp4 \ | |
-i vid3.mp4 \ | |
-filter_complex '[0:v]pad=iw*3:ih[int];[int][1:v]overlay=W*0.33:0[temp];[temp][2:v]overlay=W*0.66:0[vid]' \ | |
-map [vid] \ | |
-c:v libx264 \ |