sudo apt-get install autoconf automake libtool curl make g++ unzip -y
git clone https://github.com/google/protobuf.git
cd protobuf
git submodule update --init --recursive
./autogen.sh
make
make check
sudo make install
sudo ldconfigAuthors: John Lövrot, Max Gordon
KI Box uses the online file sharing and personal cloud content management service by Box.
| #!/bin/bash | |
| ## davfs2 installation and Box.com account configuration script for Linux | |
| ## Tested on Ubuntu, Fedora and OpenSuse | |
| ## Update 1.032615 | |
| ## This script must be run as root | |
| if [ ! $UID = 0 ]; then | |
| echo "This script needs super user privileges to run" | |
| echo "run it againg using sudo or login as root" | |
| exit 1 |
| app.directive('scrollSpy', function ($window) { | |
| return { | |
| restrict: 'A', | |
| controller: function ($scope) { | |
| $scope.spies = []; | |
| this.addSpy = function (spyObj) { | |
| $scope.spies.push(spyObj); | |
| }; | |
| }, | |
| link: function (scope, elem, attrs) { |
#Introduction
Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.
Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.
| set guifont=Monaco:h16 | |
| set transparency=0 |