Michael Ash wrote:
I'm not saying that you load it lazily on demand. I'm saying that you get the app up and running in a minimal fashion, and *then* establish the connection. Do it immediately, but after you've officially "launched". If you do it modelessly, then the user can still access whatever features don't rely on the connection. That might just be the about box, but maybe that's what they're after. If you do it modally then at least your dock icon stopped bouncing and you can easily switch to the app to check on its progress and such.
I suggest showing the long-running action using the app's normal way of showing long-running actions, whatever that might be.
An example of this is Safari, if it has a home page that takes some time to load. There's no splash or "loading" screen; Safari just presents its normal window with its normal "connecting and loading" indicator, exactly the same as if you'd clicked a link to a page that takes a long time to load.
If the only possible long-running action for the app occurs at launch, then an "I'm working" splash screen or other window might make sense. But if the app has a normal way of showing the user that an action is taking a long time to complete, I recommend using that over a specialized launch-only window.
-- GG _______________________________________________ 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]
