<br><div><span class="gmail_quote">On 19/04/2008, <b class="gmail_sendername">Stefan Küng</b> <<a href="mailto:tortoisesvn@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">tortoisesvn@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;">
Peer Sommerlund wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><span>
I'm crosposting this to all tortoises I know of - the Windows Overlay problem is relevant to all.<br>
<br>
(//git-cheetah //is a tortoise in disguise)<br>
<br></span><span></span><span> > [copy of<br>
<a href="http://bazaar-vcs.org/bzr/bzr.dev/doc/developers/tortoise-strategy.txt" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://bazaar-vcs.org/bzr/bzr.dev/doc/developers/tortoise-strategy.txt</a>]<br>
</span></blockquote><br><div><span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">[Peer] 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>
</blockquote>
<br></span></div>[Stefan] I'm not sure what exactly you want to improve here. <span><br>
</span></blockquote></div><br>After I have thought some more about it I realise that it is probably NOT a good idea to try to build a generalized stub.<br>
<br><br>The analysis by Mark Hammond indicates that script-based tortoises (TBZR and THG) will get version conflicts and bloated memory usage. The proposed solution is a small C++ client that calls a server application (in Python).<br>
<br>As you have explained, TSVN has a similar structure, but for different reasons. The client TortoiseStub allows you to select which of three modes to use (cache/shell/none), and the server TortoiseCache can crawl the file system to give faster display of overlay icons. <br>
<br>It makes sense for TBZR and THG to share code for the tortoise stub (the client), but why should any other tortoises want a common code base? <br><br>The consequence would be<br>(1) wider audience means that tortoisestub would be tested more.<br>
(2) complexity increases by generalizing TSVN stub instead of forking it.<br><br>The first is void for TSVN as they have a large audience, and the code has been tested for a while. Refactoring the code would only destabilize it. The latter is an argument against common code.<br>
<br>Conclusion: TBZR and THG should do their own stub, probably by forking TSVN code.<br><br><br>My apologies for wasting your time,<br>Peer