Shamil's Blog. Software Engineering Processes, Android, CI, Devops.

my ipad (ios 5.1.1) had spinning wheel of death boot-loop (without apple, just SWOD) after battery depletion. I had lost all apps data and notes.

WTF? passcode lock is the f%%%%%g problem.

while being in SWOD ipad detected by itunes, i could even backup photos using OS methods, not sync (without even passcode authentication, which is strange!).

I could even make transfer purchases to itunes. but no backup/restore is available because "unlock device with passcode" is needed. I know f%%%ng passcode, I WANT to enter it, why the HELL it's impossible to enter passcode in itunes while ipad is connected?!

restoring from the previous backup did not work with the same reason, device is locked with passcode. "unlock please...".

so I had to upgrade to ios 7 from recovery mode (recovery mode is really the only way in this case!).

the most ugly thing is even after it's initialized, and I make restore from backup, the ipad shows "welcome" screen. it's clean and new.

I don't rely on itunes backups anymore. that's sad.

Seems like i'm more interested in having android device than ios. These are android vs ios screen after new device init.

Labels: apple, ios, itunes, shit

2 projects (same roots for both actually) found:
- in-the-box (proj goal is to run android apps on ios)
- iSpectrum (sealed on sep 2010 when apple tighten cross-compiling rules)

My goal is to compile and run JokerME under iOS! Need to try this market for JokerME, to see devs interest.

Labels: compiling, ios, java, jokerme

A thoughts of an old-school Java programmer while learning some iOS

..are not designed to be a fast-search-answer book. (search behaves bad actually). It's a tightly linked bundle of articles (with lots of html pop-up annotations!), which you have to read one after anohter. This creates a rich market of developers books, of course. But I'm not fan of overspending :-)

This stands in direct opposition to how Sun's Java docs were presented: to understand how to use library, one need to read only the class/interface descriptions (I can't remember I read package docs, anyone?); each class description is a very short and contains the concept of how it iteracts with others.

I think it comes from language differences: Java presents more plain classes without multi-file classes (.h, .m in ObjectiveC). So with proposed (by Sun?) javadoc inline style documentation Java classes are much easier to describe and support the changes.

Anyway, I spend more time to find information even in cases when I know what I'm looking for, comparing to Java SDK or ME docs or even Android docs.

For the Apple iOS docs, single place for navigating across whole bundle of articles could be very good.

Labels: docs, ios, java, programming

I think this image is more than enough to understand the difference:

Labels: apple, coordinate, feelthedifference, ios, macos, shit