Re: SplashScreen
Re: SplashScreen
- Subject: Re: SplashScreen
- From: Chris Williams <email@hidden>
- Date: Sun, 02 Dec 2007 09:57:33 -0800
- Thread-topic: SplashScreen
Without knowing how you're doing it, what the actual desire effect is, and
what it's doing today, it's hard to advise.
While I agree with Rick in principle (splashscreens == bad) many apps simply
need them. My app, for example, is a database driven application, and
cranking up MySQL, getting the data back to where the user last was, takes a
lot of time (as much as 10-15 seconds). It's especially bad when one of
more of the disks has gone to sleep.
I didn't have a splashscreen for a while and the app appeared really stupid
with parts of the UI running and others not. Now I show the loading status
in the splashscreen and the user at least knows what's going on. Better
than just a beach ball.
My app manually creates the splashscreen window in the appcontroller code,
not loading it from a nib (unpredictable order...) and disposes of it when
at the end of applicationDidFinishLaunching. Yes, parts of the UI come up
under it, but that's the whole point...
HTH,
Chris
On 12/2/07 6:52 AM, "Eric PETIT" <email@hidden> wrote:
> I have a splashscreen at the starting of my application but I don't
> want that the application menubar appears and that an action is
> launched before the splashscreen disappears.
> Does somebody have a suggestion ?
> Thanks
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden