> If you release a piece of software into the public domain, be prepared
> to listen to the whims of its users. If you wanted TSVN to be closed
> of features that you don't like, then you should have made it closed
What do you think I'm doing here? I *am* listening to whims of users
every day for free. But I don't think it's unreasonable that I like to
keep those at a minimum if possible.
> I am sure you are clever enough to implement such an API system that
> is bomb proof. I already stated that the interface would need to be
If it would be possible to make this bomb proof, don't you think
Microsoft would have made the shell extensions that way? If it was
possible to make this bomb proof, it wouldn't be possible for shell
extensions to take down the desktop.
> simple for this reason.
> The third party plugin and its interface within TSVN could even be in
> a different thread.
Not possible on Win2k and I think also on XP. On Vista it might be
possible to move it to a different thread.
> There are hundreds of other programs that allow third party programs,
> and they don't seem to put "But what about bugs" as a showstopper, in
> any case surely a bug report, "When I run my program TSVN crashes"
> would get a farly short response.
Most apps which provide a plugin architecture do that so that plugins
can extend the features of the original application.
In your case, you wouldn't extend the features of TSVN but you want this
so you don't have a lot of work to do yourself for your specific
application (which has nothing to do with TSVN).
Sorry if I may sound rude, but I'm not here to do the work for others:
I'm here to improve TSVN, nothing more, nothing less.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-09-11 19:05:40 CEST