List view
**Implement a complete GUI for *Syncify* which equals or extends the CLI functionalities.** - User is able to track the activity of the application (Connection informations with peers, current state, download jobs with progress, conflicts). - User is prompted (with notification) of conflicts/action needed. - User is able to see the general status of the application (problem detected/synchronizing/disconnected...) in the icon tray.
No due date**Implement a simple GUI to use *Syncify*.** - User is able to create and remove shared directories. - User is able to share the link to a shared directory with permissions, in two forms (internal URI or statically hosted landing page that allows the link to be clickable). - User is able to elevate (add the writing permission). - User is able to track the downloading jobs. - User is able to resolve unsolvable conflicts (make a choice).
No due date**Implement a complete, intuitive, CLI to use *Syncify* (e.g. on a server).** - User is able to create, share, remove shared directories. - User is able to elevate (add the writing permission). - User is able to use the CLI while synchronizing. - User is able to track the activity of the application (Connection informations with peers, current state, download jobs with progress, conflicts). - User is able to resolve unsolvable conflicts (make a choice). - *User is able to output some informations on the synchronisation in a formatted manner (JSON, bash compatible...).*
No due date**Implement complete synchronisation mechanism to track and propagate changes inside the swarm.** - Peers are able to synchronise their state even if it contains conflicting changes (conflicts which can be automatically resolved i.e. no modification of the same file). - Peers are able to detect unsolvable conflicts and pause the synchronisation (wait for user input). - Peers are able to synchronise their state even if one of the peers has not the writing permissions. - Peers are able to manage synchronisation of conflicting changes when none of the two peers have writing permissions (blacklist each other until next successful synchronisation attempt, search for another peer to synchronise with). - Peers are able to detect when the swarm contains not other peer (at all or with writing permissions). - Peers are able to resolve conflict detected in changes broadcast.
No due date•2/8 issues closed