サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
体力トレーニング
petersteinberger.com
Some people think of me as the guy that does crazy things to ObjC and swizzles everything. Not true. In PSPDFKit I’m actually quite conservative, but I do enjoy spending time with the runtime working on things such as Aspects - a library for aspect oriented programming. After my initial excitement, things have stalled a bit. I shipped Aspects in our PDF framework, and people started complaining th
UITextView on iOS 7 is a lot more powerful, since Apple switched over from using WebKit to TextKit for rendering. It’s also very much a 1.0, and has some rather terrible bugs. In fact, they go so far that people started writing replacements for the whole scrolling logic. Of course, people reported these issues in PSPDFKit as well, so I had to find a workaround. I’m using contentInset when the keyb
I’m generally not a big fan of jailbreaks. Mostly this is because they’re used for piracy and all the hacks result in weird crashes that generally are impossible to reproduce. Still, I was quite excited about the recent iOS 7 jailbreak, since it enables us to attach the debugger to third-party apps and do a little bit of runtime analysis. Why? Because it’s fun, and it can inspire you to solve thin
When calling optional delegates, the regular pattern is to check using respondsToSelector:, then actually call the method. This is straightforward and easy to understand: 1 2 3 4 id<PSPDFResizableViewDelegate> delegate = self.delegate; if ([delegate respondsToSelector:@selector(resizableViewDidBeginEditing:)]) { [delegate resizableViewDidBeginEditing:self]; } Now, this used to be three lines and n
Now that Xcode 4.4 has finally reached Golden Master and you can submit apps, here’s a trick to use subscripting right now. Yes, Apple will introduce this feature in a future version of OS X and iOS, but why wait? Here’s the snippet from PSPDFKit, my iOS PDF framework, to make it work: It’s a bit crude, and Xcode won’t show any warnings if you’re doing subscripting on any object now, but you know
While writing AFDownloadRequestOperation, a new subclass for AFNetworking, I discovered that the behavior of NSURLCache changed between iOS 4.x and iOS 5.x. Before iOS 5, NSURLCache just saved requests to memory, even if the documentation said otherwise – the diskCapacity property was silently ignored. This led to some open-source subclasses of NSURLCache, which retrofit disk caching. Most popular
このページを最初にブックマークしてみませんか?
『Peter Steinberger』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く