[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-21 21:50:55 CET

SteveKing <steveking@gmx.ch> wrote on 02/21/2005 03:39:10 PM:

> Mark Phippard wrote:
> > I have a possible idea for how we could do this, I think I suggested
> > something like this several months ago.
> >
> > 1) A property would be added that specifies the name or an identifier
of
> > a program to call. The program either has to write the SELECTED bug
ID's
> > back to stdout or to a temp file that is passed as an input parm. TSVN

> > would only support one or the other (whatever is best for you). I
would
> > suggest a temp file only because in some programming languages writing
to
> > stdout is not as easy as others.
>
> A program is not the ideal way to go. This program would have to be
> installed on every users computer, not to mention the whole
> configuration (paths, params, ...) too.

I think we need to support programs, otherwise too much of the burden is
on TSVN. Also, as long as TSVN provides a default program for basic HTTP
scraping you are covering most of the open source users. People with
proprietary bug tracking tools are not necessarily going to have a problem
with installing a program to get "richer" integration.

> > 3) TSVN would supply a default program that will read and parse a URL
and
> > present choices in a selection dialog. Of course selections would be
> > written to stdout or temp file like any other program. TSVN would
either
> > support no authentication or just whatever you could reasonably
easily.
> > Again, up to you.
>
> Parsing stdout isn't easy. And (as you can see with TCVS) it isn't
> 'streamy', i.e. you can't get any progress information.

Note that what I am suggesting is that the "program", not TSVN, would
provide all UI. The only thing that goes to stdout, or a temp file,
should be the string that goes into the bug ID field. The default TSVN
program would provide a UI for itself that encapsulates any HTTP scraping
and just returns the selections.

> > 4) It would be up to bug tracking tools to provide their own client
> > program for their tool if the TSVN default program could not work for
> > them. Perhaps they just need to prompt for a username and then call
the
> > TSVN program? Or maybe they do not use http:// etc....
> >
> > 5) If the above property were set, a button would be added to the UI
to
> > select issues. This would trigger calling the program.
>
> Again, a button isn't much of a difference to starting the browser. Yes,

> I know: the automatic insertion of a selected issue. But that alone just

> isn't worth the amount of work it would need to implement this.

I think automatic insertion is the whole issue. I cannot imagine anyone
has a problem with a separate dialog. They just want to be able to select
some issue and click OK and have them filled in.

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 Mon Feb 21 21:51:37 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.