My favorites | Sign in
Project Logo
             
Search
for
Updated Oct 11, 2008 by gfxmonk
ThingsWeCantDo  
A bunch of things we have tried to do, but failed for various (mostly technical) reasons.

If you can help out getting any of these to work, you will be a bit of a hero:


Tilt Scrolling

As seen in Instapaper Pro. But I thought of it before they implemented it ;)

Why Not?

I have working code for tilt-scroll on a UIScrollView in portrait orientation. The problem is that UIWebView is not a UIScrollView, and in fact provides no method for programatically getting or setting the content offset / scroll.


Double-tap and drag to zoom

In order to use the interface one-handed, I'd like to be able to double-tap and hold (on the second tap). Then dragging would zoom in/out around the point where the tap originated.

Why Not?

Overriding touchesBegan:withEvent: in a UIWebView subclass does nothing - these events never seem to happen, despite the fact that UIWebView inherits from UIResponder.

Additionally, I tried overlaying a transparent UIView and handling the events there (as suggested in a bunch of online forums). The events now happen, but forwarding them on to the web view has no effect.

For all intents and purposes, it seems that:


Pop-up buttons on the navigation bar

To save space, it'd be cool if you could have a little pop-up when you touch (and hold) the star button on the item viewing toolbar. Then we could bundle up the "Mark as read / starred / shared" buttons into a single toolbar button.

I got the interface builder layout, and hooked everything up so that it should work.

Why not?

UIButtons provide events like "touch drag exit". If these actions did what you expect, then it would work fine. However, this event doesn't fire when the touch leaves the button area. Instead, it fires once you have left and gone a further 50 - 200 pixels from the button area (it's not the same each time). Which conveniently prevents the other buttons in a pop-up draw from actually receiving drag events.

I think it'd be possible to do this using a single big custom view. But it's probably not worth it.


Proxy Support

Working with authenticated proxies would be great, yes?

Why not?

Well, partially because downloads go through python. If this weren't the case, the proxy issue would probably go away. But I'm not re-writing everything in objective-c.

So you can use the CFProxySupport classes to deal with proxies. This doesn't compile on the simulator, so it requires a bit of connditional compilation hackery and is hard to test. But it does work.

What doesn't work, however, is the NSDictionary you get back from CFNetworkCopyProxiesForURL.

It has keys for kCFProxyUsernameKey and kCFProxyPasswordKey, but these are always empty. To get these values, you need to go via the keychain. But when I try to strike up a conversation with the keychain, I get error code -25308

I believe this error message means "Interaction with the Security Server is not allowed." It's hard to tell though, because it appears multiple times with different explanations in the documentation and on the internet.

I've given up trying to decipher this mess. It would probably be easier to somehow pipe / proxy the http requests through the native app and hope that AppKit will handle everything for us. But that's hardly a pleasant thought.


Sign in to add a comment
Hosted by Google Code