Re: [Evolution] Feature requests: modularity & imap caching...

On Tue, 2002-04-09 at 21:40, Dan Winship wrote:
seconded. Calendar, Tasklist, Summary is not used here. Why are they

I rarely use these, but a coworker uses them (same box, two different X
servers). Why not demand-load them, so one doesn't take the startup hit
until one tries to use them?

Because then everyone would complain that it took too long for the 
calendar to pop up the first time you clicked on it. :-)

Another reason which no one has mentioned yet is that the shell doesn't 
know all of the folders that will exist. For instance, if you flip the 
examples around and don't start up the mail component until the user 
clicks on a mail folder, then you wouldn't have any IMAP folders until 
you clicked on a local mail folder first, which would be annoying. 
(Likewise for LDAP folders and local contacts.)

Hmm, not really, for local stuff, the shell tells the objects what
folders it has to manage anyway, so it does know the tree for
contacts/calendar, etc.  Apart from (in mail): imap, and (external)
maildir, vfolder and spool folders.

I know Ettore was thinking recently about making component startup be 
delayed though. One way this could work would be for the shell (or 
actually, the wombat) to keep track of the complete folder tree between 
sessions. This could be nice for other reasons too.

It would be better if it didn't, its just another copy of already copied
copied copied data ... which is already hard enough to keep in sync
(disk:server <> component:disk <> shell:disk?).  And with e.g. shortcuts
it doesn't need it in order to start things delayed anyway.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]