![]() ![]() and in minutes, all the work that Dino and Gertrude did pruning and cleaning the folder(s) is eradicated as XYplorerSync populates all the deleted photos right back into the folders. If Dino were using AJCSync, GoodSync, 2BrightSparks SyncBackPro, or whatever other sync utility, he could achieve what he wants with almost no fuss.īut he's working in XYplorer, enjoying the fact that this sync feature is now built-in. She's added some new photos and deleted some photos. In the meantime, Gertrude has been making changes to the Office folder while Dino was out. When he gets back to the office, he wants to sync his work with the Office folder. While on business travel, Dino goes through the Field drive and deletes a bunch of old files he doesn't want anymore. Dino has a local fileserver drive folder "Office" and then there's a portable "Field" USB drive folder that is used to access the photos when working in the field. So let's say there's a bunch of photos in a folder for a small design company. For whatever real-world business reason (let's say you're dealing with a less tech-savvy operation and their ad hoc solution is to merge back and forth between a local and a remote location), the only option you have is to synchronize work. In a common use scenario, you have two folders that each represent ongoing work on the same content - including cleaning up those folders. ![]() I'd like to point out, though, that the 2-way sync you describe (without deletions) isn't particularly useful in my view. It would be cool to be able to set up stored Sync Jobs, in a manner similar to Catalog basically keep a list of location-to-location syncs that can be fired off without opening panes. ![]() Literally just open two locations on left and right and sync them, without setting anything up. Pane-to-pane ad-hoc sync would be awesome. But if XYplorer keeps track of state, then it knows that B had those files but they were deleted thus it knows to delete them from A. If sync occurs without knowledge of state, then those files will simply be copied from A to B again. On the B side, a user manually deletes some files one day. Why is keeping track of state necessary? Imagine a situation where several syncs have been run between A and B. Once XYplorer is aware of state, then subsequent syncs can delete files removed on one side. The first time a sync between locations runs, it's a full sync: just copying new files and overwriting old files. Importantly, XYplorer would need to keep track of file states, which GoodSync does through flat files, in order to facilitate deletions. Users would have the option to propagate deletions (and perhaps back up those deleted files somewhere for safety - but that's a nice-to-have). As with 1 above, additional settings and parameters would be great as options. The two-way sync would need to, at a minimum: (a) copy new files both left and right (b) delete files on one side that were deleted on the other side (c) overwrite older files with newer files. If you could offer some GoodSync-like options (perhaps in a special settings pane) that would be a bonus, but for common use, it could just default to essentially mirroring.Ģ. The one-way sync would simply make (ABC > CD) into (ABC > ABC) as you say. So here's what I would absolutely need in the sync solution:ġ. If we've already got employees bought into using XY, it's tedious to have them jump in and out of multiple programs to create settings and relationships with the same folders/files over and over again - when XY could be a one-stop-shop. But the reason we want/need sync tools in XYplorer is to save time and simplify things. (There are other, more- or less-complicated solutions, but this one seems the most directly relatable to the XY paradigm.) So you might review its version 10 just for gaining the vast thinking put into it, as it can handle just about every conceivable sync scenario and is quite elegant. Hi there - I'd like to jump in on this a bit.Ī quick note: I think the program GoodSync is probably the most comprehensive and well-built program to use as reference.
0 Comments
Leave a Reply. |