🚀 go-pugleaf

Hi,

As a long-time PVCS user I'm familiar with the general ideas behind VCS
systems, and I'm now evaluating how TS will fit into our development model.
I hope someone can answer some basic questions that don't seem to be clearly
covered in the TS Help.

1. TS requires some kind of relationship with a external VCS provider (e.g.
PVCS) but it doesn't seem to then operate on actual PVCS-defined project. It
makes its own. What's really going on here - is TS a complete VCS system,
only a user-interface to an external system, or something in-between?

2. The role of the "local directory" in a TS project isn't totally clear to
me. The apparent relationship is ok if one's delvelopment model defines a
one-to-one relationship between a "project" and a lcoal directory (or one
project to many directories). But what about the case where one directory
may contain sources for several projects? That may seem like a really bad
idea on the surface (and it is), but it works in certain situations: for
example, we create custom components for use in our Delphi apps, along with
some general-purpose units (non-components). We will tend to keep all of
these component and unit sources in one directory (we're talking about only
a few tens of files). Within this one directory, these sources can be
logically grouped into several "projects": obviously, I could consider all
the component sources that belong to a given component package to be one
"project"; alternately I might consider each individual component to be its
own project. In fact, I have one single general-purpose unit that I would
consider to be a single project on its own.

TS seems to be fixated on the notion that the entire content of a given
directory, excluding files rejected by the extension masks, are part of one
project. Apparently, anything in the local directory that doesn't match the
remote end is offered up in the local view as a suggested update. This is
really annoying, when 99% of the local files have nothing to do with the
current project. I have tried "Removing" these, but they re-appear every
time the view refreshes.

Isn't there a way to configure a TS project so that it knows *exactly* which
files are actually part of it, and to totally ignore the presence of other
files in a local directory, beyond the limitations of file masks? This is
the natural way that I would have extected this to work, as it does with
PVCS.

Perhaps I'm mis-using the local directory in TS's context. My local
directory example above is the actual, live, current, working, set of code
that my components are installed into Delphi from. It would be really
impractical to break this into many other directories just to match TS's
paradigm. Or perhaps the expectation is that when working with a TS project
locally I must create a seperate working directory, and manually copy
to/from the "real" local directory? All of this sounds completely absurd. I
hope someone can shed some light on this.

Thanks in advance for taking the time to read this really long message, and
for any advice you can offer.

Chris