Make available offline

[mottosso]

It's back!

Featuring

• Customisable root, one artists working on M:\ and another at /my/server works wonders
• Secure, full support for TLS encrypted transfers with multi-user authentication
• Bi-directional synchronisation, download on-demand and automatic upload on publish

Download

Upload

[mottosso]

Regarding limitations, here's the status.

• No cancelling of downloads
• No batch download of, say, an entire asset
• Closing the Loader interrupts active downloads

Multi-selection of say the latest version of every subset of a shot works, there is a counter (2) in the download status notification at the bottom, and closing the GUI preserves the download state, unless a force-close (by holding SHIFT) is made in which case download is cancelled and temporary files are removed.

Cancelling of downloads is unsupported but possible by force-closing the GUI.

[mottosso]

As for critical questions answered, A+!

• Is Selective Sync #72 possible?
• Does it make sense for the user?
• Is the UI/UX intuitive?
• What are the security implications to this approach?
• What is the performance? Is it feasible?
• Is the performance impact acceptable on the client? How about the server?

[mottosso]

Bam, this is good to go.

About using the old Loader; that is temporary. I had the implementation for Offline Files already done through git history and due to time constraints merely re-instantiated that. The goal is definitely to get this into the new loader; I've made it as decoupled as possible here, with core parts delegated to io.download and other parts easily extractable, such as the _download_manager with module-level references.