server folder to sync. It turned out to be harder than anticipated.
But now multiple accounts can be created (no way to remove them yet,
that wil come next).
On account configuration page, one can now select the remote file server
to sync. Leave blank to sync root folder.
locally AND in the server. The files will not be updated until the user
selects which of the two files is the newest one. Note that at this
time, other clients may be updating the server. So the client should
take caution to select the proper new file.
The server file is downloaded to disk and prepended with _ocs_conflict.
so that the user can open both files and compare accordingly.
A message appears notifying the user of the conflict, and the clouds
turn red. They will not be reverted back to blue until all conflicts are
cleared.
side deletes theirs. This does not yet implement file moving. If files
are moved, it will just reupload or download them because it will treat
them as new files.
A minor bug fix also. Now the watcher is removed for files that are
being downloaded or deleted. Then added again if appropriate. This
prevented the watcher from annoucing a change and attempting to upload
the changes to the server.
comparing files between the server. Now it is more reasonable.
Also, less use of the hardisk because now I implemented a
QFileSystemWatch instance. This is much better and lets me know of file
changes. Though, there is still a strain on the HD due to the constant
SQLite access that I use.
I can't figure out a nice way to find out what files were added (removed
will be fore later) without listing the entire directory and comparing
against the DB.
