Interesting new competition for DT from the programmer that made the invaluable SpamSieve: EagleFiler.
Another file database but based on Apple’s CoreData (I’m not sure if DT uses CoreData, but I guess not). It does many of the things that DT does. One obvious point of comparison with DT is EagleFiler’s simpler import facility (including a ‘print service’ to import PDFs from Preview or elsewhere). It seems to be pretty zippy, too, at imports, indexing and searching.
It’s biggest advantage, in my view, is that it’s nicely scriptable which is the main advantage I can see in DT Pro at present… although not one worth an extra $US45 to me.
EF appears to use ‘spotlight-style’ indexing rather than a concordance. A concordance may not be needed because ‘Libraries’ are not concatenated in the Database… Documents are stored in the regular file tree and can be opened in the Finder. I’m pretty certain that this will make synchronization between computers a much simpler task than in the case of DT’s database. I use Synk (decimus.net) for backup and synchronization; it uses the Spotlight database to determine which files have changed and need to be synch’d or backed-up. It looks like that will do the trick nicely with EF.
Personally, I find classification in DT is more a distraction than an aid to data structuring since I can’t use it to weight searches. I find auto-classification is too ‘hit and miss’ to be of much use. Classification may speed-up DT (I’m not sure) but CoreData seems to be un-fussed by one big glob.
EF does not have the same number of window configurations as DT (is that a limitation?) and does not claim to be ‘intelligent’ (I was never sure what that meant in DT).
It offers fewer search configurations (no ‘fuzzy’) but I find I use only one or two of the DT combos (not ‘fuzzy’) so this isn’t a problem for me. Boolean, phrase-based and wildcard searches etc.
The current version (1.0.2) doesn’t export to IPods or replicate instances (it will prevent the import of duplicates). It opens in default applications rather than an internal version (of Webkit or PDFKit)… one advantage of which is that a search for a term in a PDf file opens Preview with the search window already populated showing all instances.
I guess from the docs and general form that MT build EF as a mail archive database (it imports the valuable ‘MailTags’ tags).
Overall it looks like good value. At the same price as DT, I’m hoping that EF will force D-T to make the ‘personal’ version scriptable soon and adopt the print-services approach to importing PDFs