I'm crosposting this to all tortoises I know of - the Windows Overlay problem is relevant to all.<br><br>(<i><a id="Git-Cheetah"><i>git-cheetah </i></a></i><a id="Git-Cheetah">is a tortoise in disguise)</a><br><br><div>
<span class="gmail_quote">On 19/04/2008, <b class="gmail_sendername">TK Soh</b> <<a href="mailto:teekaysoh@gmail.com">teekaysoh@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, Apr 18, 2008 at 12:34 PM, Tom Widmer <<a href="mailto:tom.widmer@googlemail.com">tom.widmer@googlemail.com</a>> wrote:<br> ><br> > [copy of <a href="http://bazaar-vcs.org/bzr/bzr.dev/doc/developers/tortoise-strategy.txt">http://bazaar-vcs.org/bzr/bzr.dev/doc/developers/tortoise-strategy.txt</a>]<br>
><br> > TK Soh wrote:<br>><br> > I'd say the document details the best strategy for TortoiseHG too,<br> > simply by replacing BZR with HG and Bazaar with Mercurial.<br> ><br> > Except I propose this change:<br>
><br> > Share the exact same (eventually C++) shell overlay extension for Bzr<br> > and HG, so that if you have TortoiseHG and TortoiseBZR installed, they<br> > actually are sharing a single COM dll, which will presumably pick up<br>
> from the Windows registry the names of the RPC exe programs it needs to<br> > communicate with (one Bazaar one and one Mercurial one). There's a minor<br> > versioning issue here, but this can be solved by versioning the<br>
> capabilities of the RPC server so newer versions of the shell overlay<br> > extension don't ask unanswerable questions of older RPC servers.<br> ><br> > If that's no go, at the very least the C++ code can be shared in its<br>
> entirety, and just built differently for HG and BZR.<br> <br> <br>Stefan Küng of TSVN has proposed a solution to get around the slot<br> limit of Overlay handlers among the Tortoise clients:<br> <br> <a href="http://tortoisesvn.tigris.org/svn/tortoisesvn/TortoiseOverlays/version-1.0.1/Documentation.txt">http://tortoisesvn.tigris.org/svn/tortoisesvn/TortoiseOverlays/version-1.0.1/Documentation.txt</a></blockquote>
<div><br>username guest<br>password <empty> <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Eventually TortoiseHg, and probably all other Tortoise clients too,<br>
will adopt this approach.<br> <br></blockquote></div>I think that the TortoiseOverlay component could evolve into a separate project, were some of the features mentioned in the bzr tortoise strategy (space-efficient DLL architecture, separate tortoise-processes) would fit nicely, and benefit all tortoises.<br>
<br>I would like to contribute to such a project, but I would rather watch a dedicated mailing list. <br><br>The amount of mailing lists posts I'm trying to follow has reached my processing capabilities, so adding two more (TSVN and TBZR) with a fairly high amount of posts that are not relevant to me is not too attractive. <br>
<br>Anybody feel like setting up such a project?<br><br>Regards,<br>Peer<br>