[Dev] Chandler Startup time...

[Grant Bowman]

* patrickdlogan at stardecisions.com <patrickdlogan at stardecisions.com> [040521 15:47]:
> > I ran Chandler through a profiler and grabbed 
> > the top 50 hotspots. It seems like there is a 
> > lot of stuff happening in
> > the repository (which I guess is the data store). 
> 
> Jumping into the middle of this without knowing much of anything about the design of Chandler, I offer some
> ideas...

Another approach might address the end-user perception of activity.  I
noticed that even for a simple Python application that includes wxPython
modules the start-up time can be quite high while the modules are loaded
and interpreted.

Platform specific calls to the C++ functions wxSplashScreen() and/or
wxBeginBusyCursor() would give users something to look at while waiting.
Even longer duration waits might be more acceptable to users if they can
see some hint of activity.  I modified a hello world application using
the OSAFLogo [1] which can be downloaded from a temporary location.

Another more elaborate idea is a technique used by the boa-constructor
IDE.  Unfortunately wxWidgets 2.4 is required to run it.  At launch
boa-constructor shows a splash screen with progress bar and shows the
various modules printed in the window in real time as they load.

FYI,

-- 
-- Grant Bowman                                <grantbow at grantbow.com>

[1] http://www.grantbow.com/splash.cpp
    http://www.grantbow.com/OSAFLogo.bmp