Graphical Subversion Workflow, Defining the

[Daniel]

This ticket introduces signifigant changes in

The attached mock-up wireframe shows a task oriented working environment. It has a separate [file tree] view for the repository and the local working copy. It focuses on the two main tasks (checking out and committing between the two). And it has a log view that should also be used to display revision comparisons internally in the app. (some kind of built in Kompare front-end).

That was the basics covered by the wireframe. Now for more in-depth suggestions on how to make a great version control working experience.

When one or more files are selected in the working-copy, and the user press ‘Commit’ than the user should be presented with a dialog box were she can enter a revision comment and confirm that she wanted to commit the changes. When no files are selected; the entire file tree should be committed. The user should be made aware of this in the dialog/confirmation box.

When one or more files are selected in the repository, and the user press ‘Check-out’ the selected files should be checked out. When the check out process will overwrite local changes, the user should be made aware of this using dialogs and the internal Kompare front end. When no files are selected; the entire file tree should be checked-out. The user should be made aware of this in the dialog/confirmation box.

‘But...how to compare different revisions of the same file? Is not the repository view limited to the current revision?’ No. Above the file tree there should be an addressbar-like panel that displays the current revision number. The panel should also display the path to the repository. This revision number can be changed by selecting the numbers and entering a new number followed by ‘Return’. Underneath this panel there should be another panel for tabbing. (Yes. This will make the first tabbed version control user interface in history.) Each tab can hold a separate revision of a repository or indeed a separate repository! The working copy view should have similar panels (an unchangeable revision number of the currently selected file/tree, path-to-working-copy, and a tabs panels).

The internal Kompare client should be... Well, a scrollable version of Kompare. There should be a fast fading effect when switching from log view to file comparison view. To alert the user, so to speak.

...and there is nothing more I can think of just now. Probably will be more in the future. :-)

[Daniel]

Basics of new workflow

[Daniel]

Oh. Of course; when clicking on a file in the working copy view it should be opened for editing by the defult application according to KDE. Saving the file should indicate in KVersioning that it has been changed.