BzrUI

Differences between revisions 11 and 12
⇤ ← Revision 11 as of 2006-05-30 16:21:17 →
Size: 1731
Editor: catv54007E41
Comment: shouldn't be in the spec
← Revision 12 as of 2008-08-06 16:30:42 → ⇥
Size: 1737
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
This specification discusses implementing an integrated graphical user interface for the [http://bazaar-vcs.org Bazaar-NG] distributed version control system. This specification discusses implementing an integrated graphical user interface for the [[http://bazaar-vcs.org|Bazaar-NG]] distributed version control system.
Line 12: Line 12:
Providing a user-friendly frontend for source management. This will be achieved by following the [http://developer.gnome.org/projects/gup/hig/2.0/ GNOME Human Interface Guidelines]. Providing a user-friendly frontend for source management. This will be achieved by following the [[http://developer.gnome.org/projects/gup/hig/2.0/|GNOME Human Interface Guidelines]].
Line 27: Line 27:
The strings appearing in the application should be translatable (via Rosetta). The interface will probably look like [http://rapidsvn.tigris.org RapidSVN]. The strings appearing in the application should be translatable (via Rosetta). The interface will probably look like [[http://rapidsvn.tigris.org|RapidSVN]].

Summary

This specification discusses implementing an integrated graphical user interface for the Bazaar-NG distributed version control system.

Rationale

Providing a user-friendly frontend for source management. This will be achieved by following the GNOME Human Interface Guidelines.

Use cases

  • Jim doesn't like command-line tools, but he needs source control for his work. In his office he's got a Windows machine, but at home he runs Linux. He wants an interface which feels the same on both systems.

Scope

The application will provide the following features:

  • a backend that could be used by other frontends (e.g. Qt)
  • a GTK frontend with support for the following bzr commands: init, branch, add, remove, mv, ignore, diff, merge, commit, uncommit, log, check, push, pull, export, conflicts, info, mkdir, nick, revno, version, whoami
  • standalone and bzr plugin version

Design

The strings appearing in the application should be translatable (via Rosetta). The interface will probably look like RapidSVN.

Implementation

Python is preferred as programming language, so bzr's native features could be used (bzrlib). The interface will be designed using Glade and supported by the PyGTK bindings. Using these tools the application will be platform-independent.

Outstanding issues

BoF agenda and discussion

CategorySpec

BzrUI (last edited 2008-08-06 16:30:42 by localhost)