← Back to team overview

bzr-windows team mailing list archive

Re: [Fwd: Re: Call for testing: bzrw.exe: windows GUI application]

 

2009/9/4 Ian Clatworthy <ian.clatworthy@xxxxxxxxxxxxx>:
> Alexander Belchenko wrote:
>
>> Ian, do you think we need to add special status/debug console in Bazaar
>> Explorer to (optionally) show these messages?
>
> I was hoping to avoid it. If we need it, I'll add it in.
>
> What alternatives are there? Collect the output and display it
> instantly? If that was annoying enough, it would prompt us to clean them
> up. :-) OTOH, making the UI annoying just prior to bzr 2.0 & explorer
> 1.0 isn't a smart choice.

Eventually, I'd like to have all of these things reported to the
UIFactory at a higher level of abstraction, so that it can make
sensible decisions about how to report it.  For example if there's a
code-level DeprecationWarning, it shouldn't show that to the user at
all except if they ask for the bug log.  If there's a warning that say
a format is deprecated or they have uncommitted changes, it should
show that in a dialog or other message that gives them the chance to
do something about it.  The non-ui code should not be assuming the
interface is "show this text string."

-- 
Martin <http://launchpad.net/~mbp/>



Follow ups

References