On Mon, Jan 11, 2010 at 8:35 AM, Michael Jay Lippert <mlippert...@gmail.com> wrote: > #1. Wouldn't adding a panel for MQ just add confusion for those people (I'm > currently one of them) not using the MQ extension? > > Because I don't know exactly what MQ is or how it is used this may be a dumb > question, but if there are a lot of MQ commands you want to executed, > wouldn't it be better to have a separate MQ dialog? I guess I don't know > what MQ and Commit have in common. Perhaps it can be integrated w/ the > Commit dialog via an option or tab if many things, but not all are in > common?
The MQ additions would not be visible unless the MQ extension has been enabled by the user. The same is already true of the Repository Explorer. There are MQ features in that tool that are not visible unless MQ is enabled. I agree with Yuki it would be more efficient to do many of the MQ operations in the commit tool. > #2 Most of the time the command dialog does not provide any desired > information about the commit operation, and the operation is fast enough > that I would agree it is unneeded. However there are occasions when that > feedback is useful. It would be better in my opinion to add options to turn > on and off various command dialogs, rather than get rid of them entirely, > and then just set the defaults to be off. The background version of the command runner will automatically throw up a dialog showing the command outputs if the command fails. But I also agree there should be a menu toggle somewhere that tells the tool you would like to see the output even if it's successful. This is true for the Repository Explorer as well. > #3 Although I always use the toolbar, this sounds like a good addition to > me. Options are good, and I believe that many people would like to have the > space occupied by the toolbar on the commit dialog back. True, or maybe an option to turn the toolbar into a "slim bar". -- Steve Borho ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Tortoisehg-discuss mailing list Tortoisehg-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
