From: Kevin A. <al...@se...> - 2005-12-30 05:49:31
|
On Dec 29, 2005, at 4:03 PM, XXXXXXXXXXX wrote: > Hmmm...a chicken-and-egg problem...and a bit OT. > > Some of my PythonCard apps run on fairly old hardware, with the result > that the Python interpreter/runtime takes a while to start up with > nothing apparently happening as far as the user is concerned. A > loading splash screen would be good, but if this was summoned from > Python/PythonCard/wxPython then it would happen too late. > > Has anybody done any brainstorming on this and come up with a > solution, or is anyone aware of one? I remember hearing on a podcast > recently that a future version of Java will load some basic > functionality ahead of the JVM to allow splash screens to be drawn > early on, when an application is run that requires the JVM to be > loaded. I don't think Python allows anything like this, though I'd > love to be proved wrong. > > -- > XXXXXXXXXXX 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. 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. ka |