On Sun, Dec 19, 2010 at 6:06 AM, Marcus Lindblom <ma...@yar.nu> wrote: > On 2010-12-17 12:46, Peer Sommerlund wrote: >> >> On 17 December 2010 09:04, Sakari Jokinen >> <sakar...@gmail.com >> <mailto:sakar...@gmail.com>> wrote: >> >> Hi >> >> Is there a way to get new commands provided by extensions to hg >> visible also in the TortoiseHg context menu (or anywhere else in the >> GUI) . It is a bit of a drag to go to command line in windows all the >> time to use the extensions. >> > [snip] >> I'm aware that TortoiseHg ships with built-in support for some >> extensions already. What I'm interested in is a generic solution that >> would not require forking and building TortoiseHg to provide support >> for some random extension. >> >> >> >> If this is not possible currently is there any idea how big of a task >> it would be to get something like this done? And where do I start :) >> >> >> I think it is harder to provide a framework for extensions to plug into >> the GUI, than it is to code the extension GUI directly in TortoiseHg. >> The aproach is similar to that of Mercurial - you get to access the >> internals directly with all pros and cons that gives you. > > I've had thoughts in the similar direction, and one of my extensions > (rebaseif) adds an option to "what to do after pull". > > Would it make sense to recommend people to try and build small > frameworks or extension-points/hooks into TortoiseHg whenever they add > support for a specific extension? > > Thay way, thg's extensibility would grow as more extensions get > supported. Growth will be a bit uncontrolled, but it'd perhaps be a > reasonable way forward, which allows other extension-devs to build on > previous work in the same area. And we can always try to refactor wehn > we understand how to do it properly. > > Would this be a reasonable middle-ground between hack-it-in-now and > big-design-upfront, or are there other plans?
There are plans to support extension configurables in the settings tool, and in general to allow extensions to monkey patch the GUIs as they need to add functionality, but there's little point to predicting where the pluggable GUI functionality will be necessary. Feel free to add stubs where necessary to TortoiseHg dialogs to make them pluggable by extensions. -- Steve Borho ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Tortoisehg-discuss mailing list Tortoisehg-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
