Michael,
I’m a long-time user of DEVONthink who has been searching for an alternate solution that would keep my files accessible via the filesystem, (which DEVONthink does not.) I’d like to be able to access my data in the future even if the app I’m using to file stops being developed.
Obviously, this leads me to think about shifting either to EagleFiler or Together.
After evaluating the two apps for a bit, I’m strongly leaning towards EagleFiler for a variety of reasons, (first among them being that Together seems a bit buggy.) However, there is one show stopper that is keeping me away from EagleFiler at the moment.
-
If I import a web PDF into Together from a URL, I get a nice single page PDF with no extensive borders around the web page.
-
If I import a web PDF into EagleFiler from a URL, I get a multi-page PDF which chops up the web page with page breaks. EagleFiler also adds an (unwanted) extensive border around the web page.
The extensive border EagleFiler adds is annoying. The page breaks are the show stopper for me. It all adds up to a web PDF that lacks screen readability.
I have no idea where the difference in the way EagleFiler and Together import Web PDF’s comes from. But I strongly prefer Together’s way of doing so, in that it creates a far more screen-readable version of the web page.
But, as stated, I prefer the rest of EagleFiler over Together. So I wish you’d change the way EagleFiler imports web PDF’s, or at least add an esoteric preference to allow users to import web PDF’s that lack borders and page breaks.
(I’d assume I don’t need to provide sample web PDF’s for you to examine, as you can test the difference between your app and Together for yourself.)
Thanks for reading, and keep up the good indie developing work.