Re: Status information -- needs a better solution

Douglas Pearson wrote:
> Wow -- I'm a little scared to post again, but let me start off saying I'm
> very sorry if you took this as offensive. I'm not trying to insult anybody
> or deride anyone's work. I'm just expressing a problem as we see it (and I
> was careful to say this was clearly not an opinion others would necessarily
> share).
>
> All software has problems and discussing the weaknesses and potential
> solutions seems like part of the process. I guess you take any negative
> comment about the tool as a personal assault and given that, I'm very sorry
> for not approaching things more gently. Let me be clear that we think TSVN
> is a very impressive tool and being open source of course the efforts are
> lightly funded at best. But would you really rather than folks who find
> weaknesses in TSVN just shut up and go away? Certainly in future that'll be
> my choice so you don't have to worry about me riling things up again, but I
> think the tool will ultimately be the weaker for it.

I appreciate if people come here to discuss weaknesses or bugs in TSVN.
And I always fix bugs as soon as possible. But what I sometimes get
upset about are the way *how* things are reported.

> I'm not really sure that you're interested in discussing this rather than
> just flaming me again, but I'll try to respond to your points.
>
> First up, I don't see the status information of TSVN as being critical.
> Clearly you do, but I see the explorer integration as being the critical
> feature--not the same thing and I could happily live without the current
> status portion.

The overlays really are the feature that makes TSVN unique. And it's
what most people will tell you first about TSVN. So I hope you
understand a little why I got upset when you suggested to throw all that
away.

> For you 5-20MB of RAM is no big deal. Cool -- I'm not saying it is a big
> deal to everyone. But for me adding a process that consumes around 5% of
> RAM and is running all the time is a big deal. As you say, there are lots
> of processes that wish to take that same small hit on your system
> performance and when you total them up it's not unusual to be losing 20% or
> so in RAM (generally much less in CPU) to these background processes and
> then you pay for time swapping them in and out etc. So for me, I don't take
> those hits unless there's a significant benefit and for us the status
> portion of TSVN adds very little value, while the rest of the tool adds a
> lot of value (and ZERO ram/cpu hit when it's not actively doing SVN tasks).

Ok, so *you* don't really need those overlays. But almost all others
want them. So I can't disable it just for you. And adding an option,
just because one user asked for it? Ok, we could do that.

But (have you read the whole thread or just my reply?) as I already
mentioned, if you just want to get rid of the cache, you can do that.
* Settings dialog, set the exclude path to '*' and the include path empty.
* kill the TSVNCache.exe process
* delete the file "program files\TortoiseSVN\bin\TSVNCache.exe"

So, that would be three simple steps for you to do to get what you want.
And I don't have to add another option which nobody (except you) would
ever use.

I mean, if other users would ask for that too, I'd consider adding an
option for that, but not just for one user.

> As for the rant that my proposed solution wouldn't be simple--I'm not sure
> what to make of that as you then seem to suggest right after it that the
> tool is already close to supporting it. Of course, I haven't looked at the
> code for this but in general disabling a capability isn't that hard. Maybe
> for TSVN it is and the rest of the code won't work if the status icons
> aren't filled in correctly--sure it's possible and if that's the case then I
> apologize again for suggesting it would be simple.

Well, I became quite allergic to the words "simple", "simple solution",
"easy to implement" - it is always those users who reject any
workarounds or suggestions on how to solve their problem differently
which tell me that. Telling *me* what's easy or not - get my point?

> And again, please accept my apologies for hurting your feelings. That
> really wasn't the intention,

Apology accepted :)
And sorry for me being rude. As I said, I'm having a bad day. And your
mail had some 'trigger' phrases in it that just made me snap.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org