Here are some thoughts. Scanning for fonts on VFS is time consuming. One could do it with no real extra time penalty, however, if one did it at the same time as scanning VFS for Plucker documents. But such scanning doesn't always happen--it only happens when one is in the library, and not always then.
I don't want to have a slow start-up time if the prefs are set to use a font from VFS. In other words, I don't want to have to do an extra scan of VFS directories to find that font. Currently, the prefs only store the db name for the font, which isn't enough information to retrieve it quickly. One thing I could do is additionally store in the prefs a small cache of the pathnames and volumeRefs of the last three, say, VFS-based font packages used. If the document uses one of these, and the font is still at that location, all is well. But of course it might not be (volumeRefs aren't perfectly stable, and the font may have been moved). If not, then we can do the full scan of VFS directories for all fonts. So my idea is this. Only trigger a separate full scan of VFS directories for fonts when needed. If we can find the font via the cached pathname and volumeRef, all is well. If we are in the library and doing a scan of VFS for Plucker documents, we might as well scan for fonts at the same time. And if a scan of VFS directories for fonts hasn't happened yet by the time the fontform is popped up, then it has to be done then--there is no question about it. Alex _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
