All these things are being done in my GnomeSVN interface.
So far it's just a tree-browser that examines a working copy. For
each object, the table-column-headings are:
The `Status' field comes from reading the SVN/ admin info. Modified
files have an `M' there, conflicted files have a `C', and so on.
Bill Tutt <email@example.com> writes:
> Given that SVN doesn't support a working directory model (like VSS), or a
> client view mapping like Perforce (and possibly others), the exploring left
> hand pane of a UI client is going to have to browse the normal file system,
> and try and provide enough helpful user interface to deal with that fact.
> While thinking about this, I came up with some questions that the UI needs
> to ask either the libsvn_client, or libsvn_wc bits.
> What is the Working Copy Rev# of file A?
> What is the Last Modified Date of the Working Copy Rev# we have for file A?
> Answering these two questions lets us determine "Has this been touched",
> which in turn lets us do something pretty in the file list part of the UI.
> One more additional question:
> Does this directory have valid SVN meta-data?
> This allows us to differentiate between folders in the file system that are
> Working Copy directories, and those that are normal file system directories
> in the UI. Which is fairly important given my first statement.
Received on Sat Oct 21 14:36:17 2006