Syncro SVN Client
Cross Platform file history and version control management system.
Published by Syncro Soft
Distributed by ComponentSource since 2008
Cross Platform file history and version control management system.
Syncro SVN Client makes it easier to share documents and code between content authors or developers. This multiplatform Subversion front-end allows you to browse repositories, check for changes, commit changes, update your working copy and examine the revision history. Features include: full SVN repository support for SVN versions: checkout, export, import, copy, mkdir, rename, branch, tag and delete support etc. It also includes a synchronize view which helps you spot all incoming and outgoing changes.
Key features
Flexible Layout of the User Interface - The Syncro SVN Client is composed of several views allowing you to browse the Subversion repositories and your local working copies, compare and merge modifications, check the revision history. All views are dockable, meaning that you can move them to create the optimal layout for your use case.
SVN Repository Browsing - You can add multiple SVN repositories to the list accessed through different protocols (SVN, SVN + SSH, HTTP(S)) and browse them in parallel. In this way you can identify the resources you need to checkout, or even create branches or tags directly in the repository.
Synchronize with SVN Repository - In the synchronize view you can see the overall status of your working copy resources when compared to the repository resources. The view focuses on incoming and outgoing changes, where incoming ones are the changes that other users have committed since you last updated your working copy. The outgoing changes are the modifications you made to your working copy as a result of editing, removing or adding resources.
SVN Resource History - In Subversion, both files and directories are versioned and have a history. If you want to examine the history for a selected resource and find out what happened at a certain revision you can use the History view.
Local Working Copy of a SVN Repository - Each author that shares the SVN repository with other authors works on a local copy of the repository called a working copy of the repository. The local copy must be synchronized with the repository by committing the local changes to the repository and by updating the local copy with the changes committed by other authors on the repository.
Author Information at Line Level - Sometimes you need to know not only what lines have changed, but also who changed specific lines in a file. The Annotations view displays the author and the revision number that changed every line in a file the last time. The view is synchronized with the History view and the source code view: clicking in any view updates the current selection in the other two views so that the author name and the revision number are displayed for any line of the source code view.
Check Differences Between Local Version and Repository Version - One of the most common requirements in project development is to see what changes have been made to the files from your working copy or to the files from the repository. You can examine these changes after a synchronize operation with the repository, by using the Open in Compare Editor action from the contextual menu.
Visual Conflict Editing - An update operation may bring the local copy of a file in a conflict state. The conflict state can be resolved more quickly if the conflicts are edited visually in a compare view which presents the two conflicting versions side by side like a Diff application. In the compare view the user decides for each conflict the variant which will remain and will be finally committed to the repository: the local one, the repository one or a manually edited combination of the two variants.
Revision Graph - The history of a SVN resource can be viewed as a graph in the form of a tree. One node of the graph represents a revision of that resource committed to the trunk or one of the branches of the SVN repository. The icon and the background color of a graph node represent the operation that generated a revision. A graph node contains also the repository path and the revision number.