Mark Phippard wrote:
> I cannot read the spec. Looks like the site uses frames and the spec is
> being served from a weird port blocked by my firewall.
You can read them also here:
http://svn.haxx.se/tsvn/archive-2005-01/0317.shtml
>>- The commit dialog already has enough buttons. More buttons would just
>>clutter the dialog and make it too complicated. If a button, then where?
>
> 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?
> 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?).
> 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?
> 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.
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 20:24:47 2005