On Mon, Jan 11, 2010 at 23:35, 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?

Don't worry about it, you won't see MQ panel in Commig dialog until you
enable MQ extension explicitly in your .hgrc file.
In fact, Repository Explorer already has MQ panel since version 0.9.
MQ panel is appeared only when MQ extension is enabled.

> #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.

Indeed, I make it option.

FYI: as far as feedback goes, I'll use progress bar at the bottom of
Commit dialog.
When you click commit button (or press CTRL-ENTER), the progress bar starts
moving and after committing is done, it stops with status message, such as
"Finish committing".  Of course it doesn't hide raising errors. It
show small log
window contained full output from executed command.

> #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.
>
> Mike

It show toolbar in default.
Thanks for many opinions, Mike.

> On Mon, Jan 11, 2010 at 4:57 AM, Yuki KODAMA <endflow....@gmail.com> wrote:
>>
>> On Mon, Jan 11, 2010 at 18:24, Adrian Buehlmann <adr...@cadifra.com>
>> wrote:
>> > On 11.01.2010 09:42, Yuki KODAMA wrote:
>> >> Hi all,
>> >>
>> >> Before feature freeze, I'd like to tweak Commit dialog.
>> >> Here is my plan:
>> >>
>> >> 1. Add MQ panel to the left of TextView for commit log
>> >
>> > What is "commit log"?
>>
>> I meant "commit message".
>> Commit dialog has TextView widget to write commit message.
>> I want to add MQ panel the left of it.
>>
>> >> 2. Deprecate command log window after committing
>> >
>> > Is "commit log" != "command log"?
>> >
>> > (But what is it then?)
>>
>> It's "command output log".
>> Commit dialog always show CmdDialog after committing.
>>
>> >> 3. Add 'Show/Hide Toolbar' menu to 'View' menu
>> >>
>> >> #1 resolves frustrations in MQ panel on Repository Explorer.
>> >> Most operations in MQ panel need reloading of graph view,
>> >> so I couldn't operate smoothly.
>> >
>> > How does changing the commit dialog (#1) solve frustrations on the
>> > Repository Explorer?
>>
>> Reloading of Repository Explorer takes long time.
>> If Commit dialog has MQ panel, we can execute MQ commands
>> without long time for reloading.
>>
>> > Do you want to change Repository Explorer?
>>
>> No, I want to add MQ panel to Commit dialog.
>>
>> >> In order to work this out, I have to change toolbar icons in MQ panel
>> >> to vertical direction arrows.  Here is a reason why it uses
>> >> horizontals from now:
>> >>
>> >> http://thread.gmane.org/gmane.comp.version-control.mercurial.tortoisehg.devel/6236
>> >>
>> >> #2 is same approach of Pull/Push operations on Repository Explorer.
>> >> Opening output window stops smoothly work flow.
>> >>
>> >> #3 is same as Repository Explorer's one.
>> >>
>> >> If you have opinion, please let me hear :)
>> >>
>> >
>> > Currently, I don't understand. So I can't have an opinion.
>> >
>> >
>>
>> Thanks for clearing my text up.
>>
>> --
>> Yuki KODAMA
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>
>



-- 
Yuki KODAMA

------------------------------------------------------------------------------
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

Reply via email to