![]() ![]() ![]() DT’s sync mechanism is very robust, and both computers access a DT sync store (on a WebDAV server) and stay perfectly in sync, with very quick response times. My workflow involves having my DT databases stored on both desktop and laptop, and DT is always ruining on both. Perhaps not as convenient as DTTG, but not something I could not live with, especially as my use of DTTG is much more for viewing than creation of data anyway.ĮF isn’t designed, and cannot support, having a library open on two machines at once. This is not an insurmountable issue, as I would just store my EF databases in my folder that is shared between desktop and laptop via ResilioSync, and use the RS app on iOS to retrieve a file. EF does not have an iOS app, and I find having DTTG sync’d to my DT databases is very handy at times.With DT, I wind up having two separate systems, one the databases in DT and the other my file/folder hierarchy that is kept sync’d between desktop and laptop with ResilioSync.īut, I ran into three issues with EF, one a serious (but not necessarily insurmountable) inconvenience, but two that turned out to be show-stoppers (for me). Plus, my workflow is often file/folder centric with a system of tagging and Hazel rules that I don’t want to give up. ![]() The fact that it keeps tags synced between the EF app itself and Finder tags coupled with the fact that all files in a library are rather simply arranged in a folder hierarchy in a library folder is really awesome, allowing one to use EF to find things, but also to use Spotlight, mdls at the command line, or a 3rd party app like HoudahSpot to search for things is exactly what I wish DT would do. I would really like to be able to use EF, especially because the way it handles tags is really quite excellent. I gave a look to EagleFiler which was mentioned by a few folks earlier in this thread. The new user interface is better than the old DT2 version, but not as pretty as something like Things3. They already know if they should wait or “take the risk.” Most of the people that use their Macs for their livelihood-and certainly the people here-follow the tech and typically are prepared. Imagine the blowback Apple would take if their upgrade prevented a majority of their users from doing their jobs… And, I would ‘t have attempted the upgrade without a bootable copy of my existing system if I needed to rollback for some reason. Sure, I didn’t bother to install ScanSnap and am using ExactScan, but we all knew about the 32 bit deprecation. I have upgraded and have not run into anything that impedes my ability to get my real work done. The article states “Even though Apple officially released macOS Catalina last week, the upgrade has numerous very rough edges that can even stop you from getting any actual work done on your Mac.”. But “experts” saying ‘may’ and ‘could’ in this context seems like scare tactics. Of course it makes sense to use caution when upgrading software especially if your livelihood depended on it. I think that linked article is hyperbole. ![]()
0 Comments
Leave a Reply. |