- Shows a (smallish)list of (smallish)files that are stored on a server
- Allows a user to double click on a file, which downloads it to a temporary directory and opens it for editing
- Each time the user saves the file a copy is uploaded back to the server as a temporary backup
- When the user closes the application the following happens:
- The local temporary file is uploaded to the server as a new 'version'
- The temporary backups (intermediate saves) on the server are deleted
- The local temporary file is deleted
- The 'main' application that manages the initial download, deletes the temporary files (local and remote) after closure
- A small application that watches the local temporary directory and sends updated files to the server after each save
By having a second small 'watcher / uploader' application the wxFileSystemWatcher can be in the event loop of the main class.
A potentially better way might be to spawn the 'watcher / uploader' in a thread, but again I don't know if there are problems with using wxFileSystemWatcher in a thread.
Any hints or tips about this are very welcome!