No subject

with tools like WinCVS and RapidSVN. In other words, it's designed to be
a standalone GUI, one that is easy to learn and use.

There is an important UI difference though in BE vs many other VCS GUI
clients: I want the focus to be on *version management*, not file
management. (I can't see much value in implementing a poor version of
Windows Explorer/OS X Finder/Nautilus/Dolphin/etc. If you want a
file-centric interface, use your OS file manager and we'll extend it
with (1) some icon overlays to indicate their state and (2) a Bazaar menu.)

OTOH, if you want a version-control focus, use Bazaar Explorer. It's
central display for a branch will be the status of that branch and,
soon, it will provide quick and easy navigation to the interesting
tasks, e.g. conflicts => resolution thereof; unversioned files => adding
those files, etc. For a repository, it will be the branches and
checkouts associated with that repository and easy opening/management of
them. If you grab the latest copy, you'll see what I mean. It has a
mockup of the repository view. The working tree view (used for local
branches and checkouts) will have similar filtering provided with panels
for All, Conflicts, Unversioned, and Changes.

So each tool with have it's role: file managers will focus on files,
IDEs will focus on projects, BE will focus on version control. All of
them will, if I get my way, share the *same* Bazaar menu covering 95% of
the operations themselves. So switching from one to the other will be
relatively easy.