$ mkdir -p ~/Library/Application\ Support/TextMate/Bundles
$ cd !$
$ svn co http://svn.textmate.org/trunk/Review/Bundles/GetBundles.tmbundle/
$ osascript -e 'tell app "TextMate" to reload bundles'
package com.phonegap.plugins; /*or just use your own namespace*/ | |
import org.json.JSONArray; | |
import android.app.ProgressDialog; | |
import android.util.Log; | |
import com.phonegap.DroidGap; | |
import com.phonegap.api.Plugin; | |
import com.phonegap.api.PluginResult; |
cd /usr/local/Library/Formula | |
git checkout 9e18876 tomcat.rb | |
brew install tomcat |
// sign up | |
account.signUp('joe@example.com', 'secret'); | |
// sign in | |
account.signIn('joe@example.com', 'secret'); | |
// sign in via oauth | |
account.signInWith('twitter'); | |
// sign out |
It's been 3 months since I launched the proof of concept for LampNote, my platform for sharing and discovering local information. During that time it's become apparent that in its present form the site is unlikely to achieve the kind of exponential growth that will result in it becoming “the next big thing”, though it has achieved some modest success reuniting missing cats with their owners.
Since LampNote went live I've come across several sites and mobile apps which endeavour to accomplish something similar. That doesn't usually bother me. “Tell my neighbours about X” and “what's happening at Y” are still problems that haven't really been solved using the internet. It's no surprise that other people are trying their own approach with varying degrees of funding, traction and quality. Something odd happened yesterday though. I was invited via a Facebook notification to join Circle “the local network”. As I researched Circle I was simultaneously appalled and amazed, for this was a prod
put card.xml in your drawables directory, put colors.xml in your values directory or add the colors to your colors.xml file. | |
set the background of a view to card, | |
as you can see in card.xml the drawable handles the card margin, so you don't have to add a margin to your view | |
``` xml | |
<View | |
android:layout_width="fill_parent" |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
,elem.offsetTop
,elem.offsetWidth
,elem.offsetHeight
,elem.offsetParent
ffmpeg -i test.mov -vcodec libx264 -vf 'scale=640:trunc(ow/a/2)*2' -acodec aac -vb 1024k -minrate 1024k -maxrate 1024k -bufsize 1024k -ar 44100 -strict experimental -r 30 out.mp4 |