Re: Interpreter startup speed

new topic     » goto parent     » topic index » view thread      » older message » newer message 

Hey, Al, i have a silly suggestion:

Why not run a "windows server" (ring any bells?), firing up a 
minimal child process as the splash, and when the main app code 
actually begins running it notifies the "server", which shuts down 
the splash process and brings the main to the fore, and then the 
"server" shuts down (or not, perhaps there's other things it could do 
later).

Or, the splash is all the user starts, and the splash then 
immeadiately starts the main, which then uses PatRat's IPC to kill 
the splash (once the main is actually running) and come to 
foreground (or not).

Either way, you can change the splash or the code and not affect 
the other.

Kat

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu