Re: Avoiding blocking the UI while running hook scripts?

Jean-Marc van Leerdam wrote:
> Why not reverse the way Dave works: let him update the issue via the
> issue tracker and then let the tracker start the commit with a
> pre-formatted commit message (put the burden of accessing (T)SVN on
> the issue tracker, not the other way around?
>
>

One of the requirements is that Dave should be able to see the list of
changed files *before* he decides which task to associate with the
commit. I should have mentioned this, sorry.

This was why we (I) discounted kicking off the issue-tracker hook before
the commit dialog is displayed. Same problem.

If we force the issue tracker to run before the commit, or to initiate
the commit itself, and if we require that the user see the list of
changed files beforehand (and be able to interact with the list, like
set ignore flags, or revert things, or bring up the diff), then we'll
have to re-implement a bunch of the commit dialog in the issue tracker hook.

Regards,
Roger.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-04-22 11:26:29 CEST