Help designing the evolve UI

Martin Geisler martin at geisler.net
Wed Apr 23 03:02:15 CDT 2014


Pierre-Yves David <pierre-yves.david at ens-lyon.org> writes:

> On 04/23/2014 12:16 AM, Angel Ezquerra wrote:
>>> >5. No, we are not going to decide to automatically evolve everything all the
>>> >time. The step by step approach is very valuable and I would like every
>>> >early user to discover that before trying to do anything else.
>>
>> Is this completely ruled out our just for now?
>
> "Just for now"
>
> I'm sure we can do better that the current behavior. However, I find
> it very valuable to force early adopter to be exposed to step by step
> behavior. Having access to step by step open a lots of new
> possibility, I need early adopter to discover them if we want a final
> UI that exposed them in the best possible way.

I described an example where I thought the step-by-step evolving would
be interesting:

  http://mercurial.markmail.org/message/5kctrmri5cqjxclo

It didn't feel very useful or powerful to me -- I basically had no idea
if I wanted to run 'hg evolve' or 'hg evolve --any' or if I should have
updated to another commit before running the two commands.

In other words: the steps needed to bring a repository back to an
untroubled state are completely opaque to me.

> Be encourage, to think about it and make plan for a better UI. The
> behavior will most likely be change to something else before we freeze
> the UI. But changing to the direct opposite is off the table.
>
> I hope this clarify the current position.

It does and I hope se can come up with a good way to present the whole
thing to the user.

-- 
Martin Geisler
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20140423/c2e0eaae/attachment.pgp>


More information about the Mercurial-devel mailing list