>
> |
Further investigation shows that the major culprit is the custom objects plugin, which loads all the shapes. Takes over half the time (a full second on my 800MHz PIII). The other big thing is the sheets, which takes about half a second. A lazy loading of both would do wonders. The sheets there's little to do about, unless we can partially parse an XML file. Actually, same goes for objects. Except what we could do is cache the names: After loading the sheets and objects, write a file containing origin file, datestamp, and internal name. By loading that file, we can see exactly which files are needed to load which objects. If an object is asked for which is not found there, all must be loaded. When an objects is found in the list, the file must be checked for updates. Could be part of the persistence.
-- LarsClausen - 05 May 2004
|