Hello.
I'm Aleksandar Vacić, professional web developer and wine maker in the making.
Learn more about me or see what I can do for you.
When Apple updated screen res of the iPhone 4 to 640×960 on the same 3.5″ (diagonal) form factor as previous iPhones, the magic Retina Display number turned out to be 326ppi (pixels per inch). The result is an awesome display, the best I have ever seen.
iPad on the other hand has 9.7″ (diagonal) with 1024×768 resolution, which gives 132ppi. John Siracusa said that next iPad will most likely have the same improvement in display rez, meaning it will have 2048×1536 – so the iOS4′ @2x API stuff work the same.
Granted, such resolution sounds ginormous – not even Apple’s latest 27″ monitor is big enough to design interfaces that big. But if that really happen…
…how big the iPad would physically needs to be?
iPad has 1.33x aspect ratio and 9.7″ diagonal display now. 2048x1536 and with 326ppi equals to about 9650in in one very long line, or divide again to get about 29.6in2. From there, the math is easy: 1.33x * x = 29.6, means that x is 4.71in and that physical screen size of the Retina Display iPad would be 4.71 x 6.28, or about 7.85″ diagonal.
Sounds quite possible, does it not?
Some of the stuff here also apply to problems appearing during installation or use of iTunes 9 on Windows XP, Vista or Windows 2008. Meaning – do try them, it might help you solve the issues you’re having.
If you have any of these issue, this article will most likely help you.
My wife uses Windows 2003 as development machine and I had all of these happening.
Apple is — like many other companies do in the last year or two — touting iTunes 9 as compatible only with Windows XP and Vista or Windows 7. This is safe net for them. If you run Windows 2003, this is just about the same thing as XP, regarding ordinary software.
Thus, solution here is to kill the OS-based launch conditions, which good people at WebKeyDesign have already explained how to do. The solution goes like this:

InstEd — removing launch conditions

QuickTime has two conditions, remove both
Once you’re done with all of them, install them, one by one. Start with AppleApplicationSupport, then AppleMobileDeviceSupport and then continue until iTunes as the last. Ignore SetupAdmin.exe
At the end of iTunes installation, it will try to start iPodService.exe. This fails and manifests in a variety of ways. There’s an amazing number of “solutions” on the net, but remarkably none has pinpointed the actual cause.
It’s Data Execution Prevention feature of the Windows — it will kill the process as soon as it tries to run. DEP is made to prevent malicious software using private or undocumented API or doing any sort of suspected malicious activity. iPodService.exe falls into this trap according to DEP, so we need to tell DEP to let it go as exception to the rule.
Here’s how:

Data Execution Prevention is what kills iPodService.exe
You click, they appear to start but then fail. The reason is the same as above: DEP. Add both .exe files (they are in Program Files\iTunes folder) to the DEP exception window and they will start just fine afterwards.
To expand this a bit — every time you have a known, valid software failing to start, always add them to DEP and see if they work. Most likely they would.
iTunesConnect service — a web site that iPhone developers use to manage their published applications — has a separate area that will list all the synced crash reports from the application users.
However, not all of the crashes appear there, or are slow to appear. Thus, if you have a desperate problem with someone’s application, it’s a good idea to pick these up and send them to a developer.
Here’s how, in three major operations systems: Mac OS X, Windows Vista / Windows 7 and for Windows XP.
Application crash logs are transfered to your computer each time you do a sync with the device, in the iTunes. Thus, first step is to sync with iTunes:

Sync the iPhone or iPod Touch through iTunes
On the Mac, crash logs are kept at:
~/Library/Logs/CrashReporter/MobileDevice/<DEVICE_NAME>
where ~ is your Home folder. Here’s an example:

Crash logs on the Mac OS X. Device name is “iPhone AV” here
There’s the .crash file and .plist file – archive them both and send to a developer. Actually, pick all the files you find there that have the name of the problematic application.
Files are located here:
C:\Users\<USERNAME>\AppData\Roaming\Apple computer\Logs\CrashReporter/MobileDevice/<DEVICE_NAME>
AppData folder is hidden by default, so here’s how to access it. Get into your personal folder:

User folder, with Vista folder path
Now click on the folder (address) bar which will change the display into Windows folder path and add \AppData to it, then click Enter.

When clicked, the address bar changes into regular Windows folder path
This will then show the folder contents. From here, you can follow the path above until you get to the crash logs.
For Windows 7, follow the same procedure.
Location is here:
C:\Documents and Settings\<USERNAME>\Application Data\Apple computer\Logs\CrashReporter/<DEVICE_NAME>
<USERNAME> is your login username. Application Data folder is usually hidden by default, so you need to reveal it in the same way as in Vista — by typing in and pressing Enter.
And that’s it. Easy :) – rest is for developer to sweat it.
I wrote about my disappointment due to Apple’s removal of ExpressCard/34 slot in the last generation of its Macbooks. I can’t imagine this is due to cost issues — it’s probably the space constraint since they wanted to add SD card slot.
Here’s a proposal: remove the DVD drive entirely. I don’t know about you, but I have used that thing less than 10 times in last 2 years of owning Macbook Pro. It mostly collected dust and stopped working reliably rather quickly due to that same dust; last few times when I wanted to do anything with it, it spent ages trying to recognize the disk. Or even failed to read it — even Leopard original install disk, which is in pristine condition. Or last night, when it failed to write an empty DVD, which I then burned with no issues on my wife’s Sony VAIO drive.
It’s by far the worst part of the otherwise great notebook.
It’s useless outdated thing, ripe for replacement. It would free up huge space in the notebook for many, much more useful things like:
For anyone that needs the drive, they already sell external SuperDrive for Macbook Air and there’s plenty of 3rd party external packages.
What’s not to like? Eh, Apple, how about that?
Surprise appearance at the WWDC turned out to be the least welcome, at least for me. Refresh of the entire notebook line with better hardware and lower prices is fantastic and I would be tempted to buy new MBP when Snow Leopard is out (same as I did with Leopard). Especially given the fact that I would very much welcome huge increase in battery life (got to be seen to be believed).
However, I was quite shocked to see that Apple decided to remove its only expansion slot — ExpressCard/34 — while keeping the FW800 and 2 USB ports, with no additions at all. No eSATA port. No additional USB nor FW ports. No integrated SIM slot for 3G connection.
Instead of EC/34 slot, we get measly SD card reader. Wonderful, it would serve as nice dust conduit.
It’s ridiculous change. On the so-called professional machine, you’re stuck with slow connection methods, you’re stuck with consumer-level card type and you have no means to add what’s missing. Expresscards are not exactly large presence on the market but are by no means non-existing. I own two. Novatel Wireless Merlin X950D for 3G connection and Digitus eSATA 300 card. Both add the stuff pro-level notebook should have outright, but I didn’t mind getting them because the machine itself is great.
These new models are so good, but sadly crippled in the expansion area.
So, if you buy MacBook Pro you’re left with 3 ports and no other option to expand. All that with the portable machine which is a dream to own otherwise – very large hard disk, up to 8GB of RAM (amazing stuff for a 15″ which is my target size), very, very fast CPU and strong graphic card and 80% better battery life than anything else out there. You can do wonders on a machine like that. But if you do video, you’re stuck with FW800 and USB2, both 2-4x slower than eSATA so you’ll be left twiddling your thumbs while things are copied back and forth. Or if you use CF-cards (most hi-end DSLRs do) your best bet is FW-based card reader, instead of EC/34 types which connect directly to PCIe bus and offer much faster transfer rates.
I hope Apple will come to their senses — like they did with bringing FW800 back to all models — and bring EC/34 back. After all, if they wanted to add SD, they could supply simple 5-in-1 card reader that uses that slot — something Sony did with 13″ VAIOs several years back. Those things probably cost few bucks now.
The way things are now, I will not buy a new MBP. I doubt Apple will lose a moment of sleep for that, but if there’s enough of us sending them appropriate feedback, we could have something next year.