From: Michael Wood <michael.g.wood@intel.com>
To: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: [review-request] michaelw/toaster-frontend-cleanups
Date: Tue, 14 Apr 2015 15:22:51 +0100 [thread overview]
Message-ID: <552D22BB.3060607@intel.com> (raw)
poky-contrib michaelw/toaster-frontend-cleanups
commit 310409d14c1af131ac39121936a3bb66741c39dc
Author: Michael Wood <michael.g.wood@intel.com>
Date: Tue Apr 14 15:12:35 2015 +0100
bitbake: toaster: Create and use a single common layer add/remove
mechanism
This adds a common add/remove layer mechanism that will also handle
showing
the modal dialog if there are dependencies for the layer which also
need
adding. To help bring consistency this also adds a layer added/removed
alert utility function to generate the alert message. This touches all
places where layers can be added or removed to port them to this new
common mechanism.
Signed-off-by: Michael Wood <michael.g.wood@intel.com>
commit c1c7a3435dcb70d82c2f9c710140c038cc9d205b
Author: Michael Wood <michael.g.wood@intel.com>
Date: Fri Apr 10 18:15:03 2015 +0100
bitbake: toaster: Move project context variables to common scope
We have a bunch of context data which are used in multiple pages so it
makes more sense to have this in a single place libtoaster.ctx that's
accessible from each page rather than request it from every page.
Signed-off-by: Michael Wood <michael.g.wood@intel.com>
next reply other threads:[~2015-04-14 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 14:22 Michael Wood [this message]
2015-04-16 14:11 ` [review-request] michaelw/toaster-frontend-cleanups Barros Pena, Belen
2015-04-21 12:34 ` Michael Wood
2015-04-21 17:36 ` Barros Pena, Belen
2015-04-21 19:50 ` Michael Wood
2015-04-23 15:08 ` Michael Wood
2015-04-24 16:06 ` Barros Pena, Belen
2015-05-01 16:30 ` Damian, Alexandru
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=552D22BB.3060607@intel.com \
--to=michael.g.wood@intel.com \
--cc=toaster@yoctoproject.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.