type: PIN
Consumer key: 3nVuSoBZnx6U4vzUxf5w
Consumer secret: Bcs59EFbbsdF6Sl9Ng71smgStWEGwXXKSjYvPVt7qys
type: PIN
Consumer key: IQKbtAYlXLripLGPWd0HUA
| location.href = "javascript:(" + function() | |
| { | |
| var deleted = 0; | |
| var links = document.getElementsByTagName("a"); | |
| var i = 0; | |
| var d = 0; | |
| /* Copyright 2013 Google Inc. | |
| Licensed under Apache 2.0: http://www.apache.org/licenses/LICENSE-2.0.html */ | |
| package com.example.latlnginterpolation; | |
| import android.animation.ObjectAnimator; | |
| import android.animation.TypeEvaluator; | |
| import android.animation.ValueAnimator; | |
| import android.annotation.TargetApi; | |
| import android.os.Build; |
Article by Faruk Ateş, [originally on KuraFire.net][original] which is currently down
One of the most commonly overlooked and under-refined elements of a website is its pagination controls. In many cases, these are treated as an afterthought. I rarely come across a website that has decent pagination, and it always makes me wonder why so few manage to get it right. After all, I'd say that pagination is pretty easy to get right. Alas, that doesn't seem the case, so after encouragement from Chris Messina on Flickr I decided to write my Pagination 101, hopefully it'll give you some clues as to what makes good pagination.
Before going into analyzing good and bad pagination, I want to explain just what I consider to be pagination: Pagination is any kind of control system that lets the user browse through pages of search results, archives, or any other kind of continued content. Search results are the o
| //This works... | |
| String myString = null; | |
| if (myString != null && !myString.isEmpty()) { | |
| //do stuff | |
| } | |
| //Covers both cases; less verbose | |
| if (!StringUtils.isEmpty(myString)) { | |
| //do stuff | |
| } |
| import picamera | |
| from time import sleep | |
| import time | |
| import os, sys | |
| camera = picamera.PiCamera() | |
| camera.resolution = (960, 720) | |
| archive = [] | |
| SLEEP_TIME = 5 |
| chmod go-w ~/ | |
| chmod 700 ~/.ssh | |
| chmod 600 ~/.ssh/authorized_keys |
| # Files built/generated locally. | |
| # You generally won't want to commit these | |
| bin/ | |
| gen/ | |
| *.apk | |
| *.ap_ | |
| # The generated .class files, which can also be excluded | |
| *.class |
| 1. Open your ~/.bash_profile with your preferred editor | |
| This should work from the command line: | |
| nano ~/.bash_profile | |
| 2. Check to see which version of PHP your MAMP uses, and note the path, which will look something like this: | |
| /Applications/MAMP/bin/php/php5.4.10/bin | |
| 3. Add the following line (changing to match your PHP version): |
| #include <stdio.h> | |
| #include <stdlib.h> | |
| #include <string.h> | |
| /* | |
| * MCrypt API available online: | |
| * http://linux.die.net/man/3/mcrypt | |
| */ | |
| #include <mcrypt.h> |