From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Cristian Iorga <cristian.iorga@intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] hob: Error reports are done in a clearer way
Date: Fri, 28 Sep 2012 16:42:39 +0100 [thread overview]
Message-ID: <1348846959.15753.54.camel@ted> (raw)
In-Reply-To: <1348844753-7604-1-git-send-email-cristian.iorga@intel.com>
On Fri, 2012-09-28 at 18:05 +0300, Cristian Iorga wrote:
> For long errors (bigger than 200 letters),
> the text box is scrollable and resizable
> and text is selectable.
>
> Additionaly, all message dialogs are modal.
> Otherwise, a user could still interact with hob
> even in an error case, leading to potential problems.
>
> See design details in related bugs.
>
> Fixes [YOCTO #2960], [YOCTO #2983]
>
> Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
> ---
> bitbake/lib/bb/ui/crumbs/builder.py | 5 ++-
> bitbake/lib/bb/ui/crumbs/hig.py | 59 ++++++++++++++++++++++++++---------
> 2 files changed, 46 insertions(+), 18 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-09-28 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 15:05 [PATCH] hob: Error reports are done in a clearer way Cristian Iorga
2012-09-28 15:42 ` Richard Purdie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1348846959.15753.54.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=cristian.iorga@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox