Dedicated library management window for advanced configuration.
Some of the planned features involve custom library names (aliases, does not rename or move folders), toggles to lock with password, toggles for read-only (only allows downloads and browsing, no file uploads, no file deletes, no edits, no disabling/enabling or invoking duplicate fixer), a third toggle for hiding it to web clients (private/public toggle), edit the location of the folder, duplicating a library which allows to pick a new location as long as we have enough space, another option for exporting a whole library as a .zip file (allowing us to pick the location), and rearranging orders will remain present.
This needs further planning, since I´m already thinking about a micro-management button that will allow to cherry-pick options and permissions for WebClients (for example, allowing or forbidding bulk downloads, allowing or forbidding whole library download, and the other toggles for visibility and password locking here).
User requested multiple paths for a single collection in VaM Hub, requires triage and considering technical implications among other features like package merging features for saving space.
// C# style object to mentally understand how to describe a library, its properties and settings.
class Library {
///<summary>This flag defines if sub-folders should be scanned or not.</summary>
bool scanForSubfolders;
///<summary>If the library is public, then this library will appear in the list of selectable libraries, otherwise it will be hidden and inaccesible to any web client even if it has been authorized.</summary>
bool isPublic;
///<summary>If this flag is enabled, in order to open and view a library's contents you need to re-authenticate with the master password.</summary>
bool requiresAuth;
///<summary>A read-only library will prevent any client (even if authorized) to write to this library, it will prevent any action that implies modifying packages in the library: delete, rename, optimize, disable/enable, upload, etc.
Other actions that do not write to the library can be performed like downloading packages, multi-selecting for bulk downloads into a .zip file or even downloading the entire library in one click.
bool readOnly;
///<summary>Self explainatory, if enabled it will prevent the library and individual packages from being downloaded even if you have been authorized with a password. (Web clients only)</summary>
bool preventDownloads;
///<summary>The list of directories that will be scanned, all packages will be shown in the same view as if it was one single massive library.</summary>
Path[] directories;
///<summary>Visible name for the library.</summary>
string libraryName;
///
#region Actions
///<summary>Asks for a path through file browser dialog, and copies the entire library to this new folder as long as we have enough disk space. The selected folder is added as a new library onto the application.</summary>
void Duplicate();
///<summary>Exports the entire library as a zip file, in desktop mode it should allow you to pick where to save the .zip file, in a web client the .zip will be downloaded like a normal web download.</summary>
void ExportZip();
#endregion
}
Dedicated library management window for advanced configuration.
Some of the planned features involve custom library names (aliases, does not rename or move folders), toggles to lock with password, toggles for read-only (only allows downloads and browsing, no file uploads, no file deletes, no edits, no disabling/enabling or invoking duplicate fixer), a third toggle for hiding it to web clients (private/public toggle), edit the location of the folder, duplicating a library which allows to pick a new location as long as we have enough space, another option for exporting a whole library as a .zip file (allowing us to pick the location), and rearranging orders will remain present.
This needs further planning, since I´m already thinking about a micro-management button that will allow to cherry-pick options and permissions for WebClients (for example, allowing or forbidding bulk downloads, allowing or forbidding whole library download, and the other toggles for visibility and password locking here).
User requested multiple paths for a single collection in VaM Hub, requires triage and considering technical implications among other features like package merging features for saving space.