[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: UI needs some data questions

From: Bill Tutt <billtut_at_microsoft.com>
Date: 2000-12-21 18:00:45 CET

Heh, oh sure, tempt we with the data, and then don't tell me which
functions give me the data.... :)
Do we have the "IsValidSVNDirectory()" function yet?

Bill

 -----Original Message-----
From: Karl Fogel [mailto:kfogel@galois.collab.net]
Sent: Thursday, December 21, 2000 6:34 AM
To: Bill Tutt
Cc: dev@subversion.tigris.org
Subject: Re: UI needs some data questions

Bill Tutt <billtut@microsoft.com> writes:
> 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?

This information is stored, yup. And there are (or will be)
interfaces to retrieve it -- you don't have to parse SVN/ metadata
yourself.

> 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.

Also recorded (via timestamp, and possibly later checksum).

> One more additional question:
> Does this directory have valid SVN meta-data?

Yup. The presence of an SVN/ subdir is not the only qualification --
actually, the spec is that once SVN/README is written, then we have a
valid working copy dir. So when creating new wc dirs, we make sure
that SVN/README is the last thing created in SVN/. :-)

Of course, again, you don't have to know this, you just have to use
the right function to ask the question.

> 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.

Definitely!

-K
Received on Sat Oct 21 14:36:18 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.