Original

Original

1. Download JDK 7
2. Open the DMG
3. Run pkgutil --expand "/Volumes/JDK 7 Update 60/JDK 7 Update 60.pkg" "/tmp/JDK 7 Update 60.unpkg"
4. Go to /tmp/JDK 7 Update 60.unpkg
5. Open the Distribution file in your favorite editor (I recommend (Sublime Text)[http://www.sublimetext.com])
6. Change the function pm_install_check() to always return true
7. Run pkgutil --flatten "/tmp/JDK 7 Update 60.unpkg" "/tmp/JDK 7 Update 60.pkg"
8. Run open "/tmp/JDK 7 Update 60.pkg"

The installer should skip the OS version check and you should be able to install without any problems.

The first step is install rsub on Sublime Text, it's available on Package Control. Then you should change you ~/.ssh/config to forward the port that you'll be using to your local machine:

Host my_server
  Hostname 123.45.67.89
  RemoteForward 52698 127.0.0.1:52698

Once that is done, log into your server (ssh my_server) e download rmate (yes, the same one we would use for Textmate) there: curl https://raw.github.com/aurora/rmate/master/rmate > rsubl. The last step is to move it to the bin volder and give it execution permission. In order to do that run the following:

• sudo mv rsubl /usr/local/bin
• sudo chmod +x /usr/local/bin/rsubl

From now on, as long as you have Sublime Text open in your computer, just run rsubl file.rb and it will open the file in your editor. Change it and that's it, every save on that file will auto save it remotely. It also supports sudo, so you can change your config files directly in Sublime Text.

Don't forgert to open the port in your firewall if you are using one.

But there is a way for you to improve date parsing performance, you can use the SQLite library to make the conversion. You may have to write a few more lines to get the same result, but the performance gain is totally worth it.

Let's take this date as an example: 2013-09-07T23:45:00Z, if you want to convert that to time interval you could do this:

sqlite> SELECT strftime("%s", "2013-09-07T23:45:00Z");
1378597500

We can achieve the same result on iOS using the following code:

sqlite3_stmt *statement = NULL;
sqlite3_prepare_v2(db, "SELECT strftime('%s', ?);", -1, &statement, NULL);

sqlite3_bind_text(statement, 1, [dateString UTF8String], -1, SQLITE_STATIC);
sqlite3_step(statement);
sqlite3_int64 interval = sqlite3_column_int64(statement, 0);
NSDate *date = [NSDate dateWithTimeIntervalSince1970:interval];

If you want to compare the results, Anurag Mishradid a script to demonstrate this. In his tests the performance gain was 1400%, or from 106 seconds to just 7.

If you want to read more on how SQLite parses the date in it's C lirabry you can go here.

Using a script in your build phase, you can run a shell script to determine the version number and inject this into the Info.plist of a build.

It will change your plist based on the last git tag that you have. If that is the current SHA it will show the version as 0.9.2, otherwise it will show how many commits since the last tag and the short version of the current SHA (0.9.2-2-d955863).

If you have uncommited changes (besides the plist) it will add a -dirty tag to the end of the version.

It will also update the build number with the number of commits in that branch, because of that remember to always release your builds from the same branch to prevent duplicated build numbers.

The last thing it will do is adding a GitSHA to your plist, I think that's very usefull when submitting bug reports from within the app.

You can add this script as a build phase in your Xcode project:

# Update build version with number of commits
BUILD_NUMBER=$(git rev-list HEAD | wc -l | tr -d ' ')

# Set git SHA for this build
GIT_SHA=$(git rev-parse --short HEAD)

# Update version string with build number
LINES_CHANGED=$(git status --porcelain | wc -l | tr -d ' ')
PLIST_CHANGED=$(git status --porcelain | grep "${INFOPLIST_FILE}" | wc -l | tr -d ' ')
if [ "$LINES_CHANGED" == "1" -a "$PLIST_CHANGED" == "1" ]; then
    GIT_RELEASE_VERSION=$(git describe --tags --always)
else
    GIT_RELEASE_VERSION=$(git describe --tags --always --dirty)
fi

# Update plist with new values
/usr/libexec/PlistBuddy -c "Set :CFBundleShortVersionString ${GIT_RELEASE_VERSION#*v}" "${PROJECT_DIR}/${INFOPLIST_FILE}"
/usr/libexec/PlistBuddy -c "Set :CFBundleVersion $BUILD_NUMBER" "${PROJECT_DIR}/${INFOPLIST_FILE}"
/usr/libexec/PlistBuddy -c "Set :GitSHA $GIT_SHA" "${PROJECT_DIR}/${INFOPLIST_FILE}"

If you don't want to change your plist you can change only the product plist by replacing the last lines with this:

defaults write "${BUILT_PRODUCTS_DIR}/${INFOPLIST_PATH%.*}" "CFBundleShortVersionString" "${GIT_RELEASE_VERSION#*v}"
defaults write "${BUILT_PRODUCTS_DIR}/${INFOPLIST_PATH%.*}" "CFBundleVersion" "${BUILD_NUMBER}"
defaults write "${BUILT_PRODUCTS_DIR}/${INFOPLIST_PATH%.*}" "GitSHA" "${GIT_SHA}"

View

Read it here

Well, that last part is almos true. The problem is that lots of developers have not updated their software to support the new screen from Apple.

So from time to time I have to "hack" some of my apps to make the icon look good again, specially the ones that sits in my top bar.

If you use Take Five but can't stand all the blurriness like me, try replacing this images (and adding new ones) in the app package.

Download

With that in mind I decided to combine this together and I created my own list of Emoji shortcuts.

Here it is: