Ivan Zhakov <email@example.com> wrote on 07/08/2005 04:27:16 PM:
> On 7/8/05, Mark Phippard <MarkP@softlanding.com> wrote:
> > Ivan Zhakov <firstname.lastname@example.org> wrote on 07/08/2005 03:41:50 PM:
> > > On 7/8/05, Mark Phippard <MarkP@softlanding.com> wrote:
> > > > In my opinion, if it does not include any status information, and
> > not
> > > > capture file events in the IDE, then it is hard to call it
> > integration.
> > > What do mean as "status information"? Working copy status dialog not
> > I mean status decorators within the IDE.
> Overlay icons in project tree? At the first stages it can be replaced
> "Working copy status" dialog.
Agreed. To me, the one "must-have" feature (eventually) is a way to
capture delete/move/rename/copy activity with the IDE and do them properly
with Subversion. That is the one feature that you cannot arguably handle
well today by just using VS.NET and TSVN side by side. With refactoring
being all the rage I assume people must need to do this in VS? In
Eclipse, that is one of the critical features that Subclipse provides. It
is not that easy to do and requires that the IDE API was designed to allow
> > I am not sure, yet, that this needs a special name. Ultimately, a
> > TortoiseSVN install might just do all that is needed to "register"
> > as appropriate so that it can be used in other environments. It would
> > easier to think of TortoiseSVN simply containing these features the
> > way that a PVCS or SourceSafe does.
> TortoiseVs was an suggested name only for dll and discussions. Sorry
> for confusion.
I thought that might be the case. I just wanted to clarify.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Jul 8 22:52:38 2005