[rfc] developer documentation on user interaction

[Alexander Belchenko]

Martin, you put me in the CC list of this e-mail, so I suppose you expected to get some feedback.  
I finally read your document. Sorry for not read it before.  
  
I can say that this document is too shallow for me to comment.  
  
I have 2 problems with current bzrlib output:  
  
1) I  want to have more fine-grained control in qbzr over bzr script output, we have our own UIFactory but currently it does not entirely solve all our needs because there is a lot of messages which printed to both stdout and stderr without UIFactory usage, e.g. via Command.outf or trace.py methods (note, warning etc.)  
  
2) It seems only me feel responsibility over building GUI bzrw.exe launcher required for Bazaar Explorer. We need to get rid off black console window behind bzr-explorer. This should be done only via GUI bzrw.exe. Such application NEVER NEVER NEVER should try to emit anything to stdout or stderr. Currently this is problem I'm ever have no idea how to start working on it. If all interaction with stdout and stderr can be canned into UIFactory it will be HUGE win for both GUI products.  
  
I don't know what should be right or wrong. I can only provide some vague feedback.  
  
John mentioned hg approach to use ui object passed to all commands, but he seems not very keen to this idea. I think at least such idea can be carefully investigated first.  
  
And sorry for the rest of too emotional messages in this thread below.  
Sorry sorry sory.  
  
--- Исходное сообщение ---  
От кого: Martin Pool <mbp at canonical.com>  
Кому: Bazaar <bazaar at lists.canonical.com>, Gary van der Merwe <garyvdm at gmail.com>, Alexander Belchenko <bialix at ukr.net>, Ian Clatworthy <ian.clatworthy at canonical.com>  
Дата: 24 сентября, 06:47:18  
Тема: [rfc] developer documentation on user interaction  
  
  I was doing some cleanups to improve testability of ui (shaving yaks a  
bit) and wanted to describe how bzrlib core is meant to interact with  
the user, and how it could work better. I propose to commit this  
short document to the developer guide, but I'd also like wider  
feedback on  
  
- whether it should cover anything else about how we work now  
(obviously it's not exhaustive)  
- whether we should aim for something different in the future  
  
--  
Martin <http://launchpad.net/~mbp/>  
  
  
  
  
  Будьте в авангарді моди восени!  
Поспішайте отримати безкоштовний каталог Cellbes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20090926/45de157f/attachment-0002.htm