[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: SteveKing <steveking_at_gmx.ch>
Date: 2005-02-21 22:33:00 CET

Steven H @ orcon wrote:
>>- The available bug ID's should be fetched automaticaly without any user
>>intervention. Then, they should show up like the autocompletion while
>>the user is typing --> a special char has to be defined to trigger it.
>>How define that trigger char? Separate property? Regex?
>
>
> Defined by a regex can can be swaped in and out.
>
> A user could type
>
> ---
> closes #1, fixes #5
> ---
>
> Autocomplete will fire upon a regex that sniffs 'closes' & 'fixes' - other
> terms could also be used - just list them in the regex.

I was thinking about that too. But it would have to be a different regex
string than the bugtraq:logregex one since it would have to match the
first part of the whole bugtrack string.

> I have to say that this would be an AWESOME addition - but hell it would be
> complex!
>
> I think that it is the job of the issue tracker to supply a 'report' which
> can be called upon - how?

The report isn't that of a problem. If you read the specs I mentioned
before, you can see that a well defined XML file would be enough. And
issuetrackers surely don't have a problem with generating XML files.

The problems here are:
- how to get the username to filter the whole list of issues
- how to prevent an authentication dialog interrupting the user

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Feb 21 22:35:03 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.