From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/3][V2] Hob Notebook Implementation
Date: Tue, 13 Mar 2012 11:10:36 -0700 [thread overview]
Message-ID: <4F5F8D9C.3020007@linux.intel.com> (raw)
In-Reply-To: <cover.1331558220.git.shane.wang@intel.com>
On 12/03/12 06:23, Shane Wang wrote:
> This patchset is to implement Hob self-defined notebook, and use it in the build details page.
I have raised some concerns with the implementation of this series on
each of the patches. It may seem nit-picky but we really do need to
start paying attention to the details at this point and polishing the
functionality and work-flow of the new Hob.
I'm torn on the series. As it stands we see errors each time we use Hob
in master as the standard Gtk notebook doesn't support some of the API
in the Hob notebook that is being called - errors look bad.
However this series has some poor coding style and doesn't match the
visual design - these also look bad, though arguably less so.
I don't mind whether we merge this and iterate on the implementation or
hold on merging until we fix the implementation but I feel we need to
address the issues.
What are others thoughts?
Joshua
--
Joshua '贾詡' Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-03-13 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 13:23 [PATCH 0/3][V2] Hob Notebook Implementation Shane Wang
2012-03-12 13:23 ` [PATCH 1/3] Hob: implement a self-defined notebook visual component for Hob Shane Wang
2012-03-13 18:08 ` Joshua Lock
2012-03-13 19:08 ` Oren Leaffer
2012-03-13 19:23 ` Joshua Lock
2012-03-12 13:23 ` [PATCH 2/3] Hob: use HobNotebook to implement a notebook in build details page Shane Wang
2012-03-13 18:09 ` Joshua Lock
2012-03-12 13:23 ` [PATCH 3/3] Hob: show indicators on the tabs of the Hob notebook Shane Wang
2012-03-13 18:12 ` Joshua Lock
2012-03-13 18:10 ` Joshua Lock [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=4F5F8D9C.3020007@linux.intel.com \
--to=josh@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.