On Tue, Mar 8, 2011 at 5:45 PM, Matt Neuburg <[email protected]> wrote: >> when they tap the "photo library" >> button, we (as Kyle said) "throwing up a modal 'please wait' UI" > > Rather, I'd ask myself why the user is able to tap the photo library button > at all, if the photo library is not available. Don't make the user wrong by > providing a button and then punishing the user for tapping it. The button > should instead disappear, perhaps, or become inactive, or be replaced by a > spinning activity indicator. This is why we're maintaining state in the > controller; at any given moment, the interface should reflect the state of > things and the range of possible steps that the user can perform, and the > controller can consult its state to make it so. Even if you were to switch > temporarily to a modal view that just says Saving, that's better than having > a button that slaps the user's hand. That's my philosophy, anyway... But this > is no longer an architectural matter, but a sheer problem of philosophy and > how you want the user to feel about your app. m.
Allowing the user to perform an action that requires some work isn't punishing the user. Now allowing them to cancel the operation without a good reason is punishing the user. There's no reason to load all the camera roll contents before the user requests the camera roll. Let the user tap the button and throw up a *non-modal* progress indicator that still allows them to back out of the camera roll if they don't want to wait. If they haven't backed out by the time the background loading is complete, take away the progress indicator and show them the contents. --Kyle Sluder _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
