> >From a user point of view I would find this a step back. Shell integration > is a strong selling point to Windows users.
I would agree to this. Explorer is always there and it is nice to see the repository state right away, without starting any additional application. Another point is Explorer is everywhere on Windows and having file state icons in your File/Open or File/Save dialogs is also a very nice feature. I started using Mercurial/TortoiseHg after a rather prolonged usage of WinCVS. WinCVS is a separate application that has something very close to a specialized file browser (probably similar to what you are going to achieve). I still do have to use WinCVS from time to time and the necessity to start a separate application each time is much more cumbersome than the current TortoiseHg shell integration. And I believe TortoiseHg will go the same way if it goes to its own file browser: it will become a single monolithic application. I like the current ease of having almost any function just a single (or a couple) mouse clicks away. > >From a project point of view there currently isn't the resources required to > maintain shell integration. > > I think my vote is -0 ... do it if you must. > Agreed again. The lack of resources is a severe thing... Still my vote is against it if you can. ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Tortoisehg-discuss mailing list Tortoisehg-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
