Hello People,
Today, we want to show you something that will prove just how serious we are about our promises on forthcoming features.
In spite of a lot of energy still going into fixing up the beta release, Mudi has dedicated some time to progressing on our synchronization module project.
We now have what we think is a solid framework, with obvious polishing needed in all its details, but we have all core functionality working.
As pictures tell a thousand words, here’s a screenshot of a ForkLift window with sync:

Now the thousands words
ForkLift will have one-way sync. Though most of the user comments were recommendations on models that do two-way sync, we believe ForkLift has a very advanced UI, which will eventually compensate. User input also suggested that a simpler, but faster tool is the thing to aim for.
When launched, sync will check the contents of the active pane against the contents of the folder opened in the opposite pane. The list will show
*if a file exists in the source folder, but not in the target folder (add new items)
*if a file with a newer modification date exists in the source folder, but not in the target (update items)
*if a file exists in the target folder, but not in the source (delete orphaned items)
You can use the corresponding checkboxes to decide which operations you want to execute. The file list only displays the items where a change (copy/update/delete) will occur.
Synchronization will of course work between any locations, remote or local, so you will be able, for example, to backup your FTP contents to an Amazon S3 storage with the click of a button.
So let’s hear what you think of it this far. Please use our Great Synchronization Thread.
Happy Thanksgiving