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

Re: [TSVN] bugtraq feature extension

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-02-22 22:54:19 CET

SteveKing <steveking@gmx.ch> wrote on 02/22/2005 04:42:52 PM:

> > I think you are nuts on this one. When is the last time tigris.org
> > updated anything? SourceForge usually isn't very quick to update
> > either. I think if you did not have some kind if direct control over
> > the server, odds are you would NEVER see this feature added.
>
> You already need direct control over the server to add the pre-commit
> hook scripts which associate the commit with an issue. So tigris.org or
> even SF (which still doesn't support Subversion btw) wouldn't work
anyway.
> And generating the XML file is much easier than provide the hook script
> and make the issue tracker tie the commit to an issue.

I suppose you are right, it isn't likely you would be using SF or tigris
for issue tracking but have your own repository.

> > way could work fine. I was just thinking that since authentication
> > will still be an issue, it would be better if the "Select UI" were
> > its own user-initiated dialog. That way any login prompts the client
> > has to supply are more predictable.
>
> But if the client script/program shows the UI with all the issues, we
> would need some kind of IPC to make TSVN know the issue the user clicked

> on...

What I was suggesting is that TSVN passes a temp file as a variable to the
process when it starts it and waits for the process to end to read the
file. The client would write the string that should appear in the Bug ID
field to the file. Like: 123, 234, 561

The alternative is the same thing, except instead of writing the selected
issues to the file, the process writes a specific XML format of all
possible issues and TSVN then reads the file when the process ends and
uses it to fill a list box or other UI. The only UI the client might
provide is whatever is needed to produce the list, such as gathering
authentication information. This might be the better way to go, but if
you did, I would still suggest that TSVN do it with a separate select
dialog so that the authentication was predictable. This would also give
you more opporunity to provide UI flourish, such as showing the issue
description and enabling a hyper link to the issue.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Feb 22 22:57:19 2005

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

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