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

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.)

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.

-- Dan

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