SteveKing <steveking@gmx.ch> wrote on 02/21/2005 02:24:05 PM:
> Mark Phippard wrote:
> > A Browse ... button right beside the bug ID field would work. Or an
> > integrated "..." in the edit field? Not sure if you can do a control
like
> > that.
>
> There's not much room there. Integrated in the edit field? Don't know
> how that would look like/work?
As an example, open the VS .NET properties on the TortoiseShell project
and then look at the Additional Include Directories field under C++. That
is what I mean about a '...' button integrated with the field.
> > I think a button that brought up a select dialog would be better, and
it
> > somewhat solves the login problem. It sounds like you now want to
support
> > typing directly in the log message? I guess there is nothing wrong
with
> > that, but I personally prefer the separate bug ID field.
>
> It would solve the problem with interrupting the user for
> authentication, yes. But it wouldn't solve the problem of the
> authentication (a different problem I didn't mention before: there are
> so many different authentication forms out there - which one should TSVN
> implement?).
I do not see how TSVN could reasonably support anything other than HTTP
basic authentication. You are right, that is a real problem. Most sites
use form-based authentication and I do not see how you realistically
handle that.
> > Could you use the Windows username and possibly have a setting to
override
> > to a different value? I do not think the username will be that
important.
> > Most bug trackers would have a special URL for "My Issues" and it is
the
> > login process with the issue tracker that would determine the
username.
>
> Using the windows username is a bad idea. See my answer to Erics mail.
>
> >>- Issue trackers usually require the user to login first. This
requires
> >>authentication (user interaction). Since the list should be fetched
> >>automatically, this would interrupt the user while (s)he is typing the
> >>log message --> not very UI friendly! Better ideas?
> >
> >
> > If you use a separate dialog instead of auto-complete this would not
be as
> > bad a problem. I agree that you cannot just pop-up a login dialog out
of
> > nowhere. There would have to be some user initiated event that
triggers
> > it.
>
> But what's the difference between klicking on a button in TSVN to
> klicking on the browser button to start that one up?
The difference is that you cannot select an item in your browser and have
it filled into the field in TSVN. If TSVN made a selection dialog, that
could happen. That seems like the key feature. Otherwise, you are right,
you could just have a way to launch a URL and let the user cut & paste.
> > It sounds like you only plan on supporting http:// https:// and
scraping
> > the page yourself using RegEx? I think it would also be nice to
support
> > some syntax for the URL that would allow a local program to be
invoked.
> > Perhaps the program would have to write to stdout and you would
capture
> > it, or maybe a temp file could be passed to the program and you could
read
> > the contents of the file after it finished?
>
> The program could simply register itself as a new protocol handler.
That is potentially how it could be handled. However, if you are planning
on creating your own http:// connection and reading the stream, that would
not work with a protocol handler. At least, I assume it wouldn't. In
other words, it isn't as if you would be using the existing protocol
handler for http://, you will be doing this all yourself.
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 20:37:33 2005