SteveKing <steveking@gmx.ch> wrote on 02/21/2005 01:07:33 PM:
> Over the weekend I thought about how to implement the specs Nick
> Gianakas made in january. You can read the specs here:
> http://www.wheeloyum.com/BugtraqExtension.txt
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.
> But there are some problems I don't have a solution for, so I thought I
> ask you guys - maybe you know how it should be done:
>
> - 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.
> - 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?
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.
> - The username just _can't_ be inserted in the URL to request the bug
> ID's. The reason for that is that the username is not known! I tried to
> read the username from the auth area/registry, but it's stored inside a
> folder where the name is an md5 hash of the credentials - and they're
> not known until the commit! --> But without the username available to
> filter the list of open issues, the list might (and will) get just too
> big. If you don't believe me, just have a look at the subversion issue
> tracker and their list of open issues:
> http://subversion.tigris.org/issues/buglist.cgi?
>
component=subversion&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED
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.
> - 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.
> Do you guys have ideas on how to work around/solve this problems? Any
> idea is welcome here! Otherwise I have to reject this feature, which I
> think would be unfortunate.
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?
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:00:34 2005