Re: [Pythoncard-users] Loading/splash screens

[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]

On 30/12/05 05:49, Kevin Altis wrote:
> I would go ahead and ask on wxPython-users as I suspect this is 
> something one of the other developers has dealt with in the past. You 
> could add some calls to time various spots in the startup process, but 
> disk caching, first time compilation of to .pyc files, etc. will mean 
> you'll get different results each time.

...and just to confuse things a bit more, I presume that when I use 
McMillan to create an executable, then any work I've done delaying 
imports until they're actually needed (rather than sticking everything 
at the start) is probably negated to some degree as the whole 
application becomes one executable and a lot of DLLs.

Mind you, it seems to be the interpreter that's taking the time to load, 
so...

> In the end my guess is that you might have to do something that will 
> make your code less portable such as using ctypes or win32 to load 
> something small right at the beginning of your program to display an 
> image or message on screen and then wait for the rest of the app to load.

I like ctypes (I don't have to throw away all the old C DLLs I've 
created over the years :-)) but that will also require the Python 
interpreter to be up-and-running. So it's looking more and more like 
I'll need to roll my own C "stub" to create the splashscreen and somehow 
disappear once the Python interpreter is loaded. Yikes.

Thanks for the suggestions....I need to do some more research!

-- 
XXXXXXXXXXX