Re: [Pythoncard-users] Re: Loading/splash screens

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On 30/12/05 12:34, Thomas Heller wrote:

> I have a 800MHz P3 box with 512 MB with XP SP2 for testing.
> 
> Times are for py2exe created applications.
> An application with a custom GUI based on ctypes takes far less than a
> second to show the window.  A wxPython app takes about 3 seconds.
> If this is too slow for you, or your system is slower, see below.

My hardware might be on the slow side. After rebooting, my P3 takes 
about 12 seconds to get the wxPython demo splashscreen and about 15 
seconds to start up my PythonCard application from the .py file. My 
McMillan'd executable of the same app takes 10 seconds.

A 2.8Ghz Celeron laptop with 4200rpm drive and (apparently) crappy 
motherboard architecture gives me approximately the same results. This 
is all testing after a reboot each time - if I repeat the run without 
reboot then disk caching, etc. must kick in because the times drop to 
2-3 seconds.

OK, I admit it, I'm impatient :-) Unfortunately I'm also dealing with 
users who, if there's no on-screen feedback, will start double-clicking 
again and, hey presto, before you know it there are four copies of the 
application started.

> For a C programmer it should not be a problem to extend the py2exe
> sources to include a dialog resource, then call CreateDialog somewhere
> to create the spash screen.  The C code could DestroyWindow the dialog
> just before starting the Python main script, or you could even expose
> a DestroySplashscreen function to Python which would then destroy the
> dialog after the GUI is initialized.

Ooo...sounds interesting. Thank you - I'll take a look.

-- 
XXXXXXXXXXX