All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: poky@yoctoproject.org
Subject: [PATCH 00/10] BitBake GUI fixes
Date: Mon, 6 Dec 2010 15:59:59 +0000	[thread overview]
Message-ID: <cover.1291651199.git.josh@linux.intel.com> (raw)

This series of patches fixes the BitBake GUI's and some of the code they
interact with such that I can now successfully use the goggle UI with the
XMLRPC server.

The series is currently pretty useless due to bug#561
(http://bugzilla.pokylinux.org/show_bug.cgi?id=561) preventing use of the
goggle UI with the none server however I would appreciate review on the patch
set before it becomes to large.

Pull URL: git://git.pokylinux.org/poky-contrib.git
  Branch: josh/master
  Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=josh/master

Thanks,
    Joshua Lock <josh@linux.intel.com>
---


Joshua Lock (10):
  bitbake/crumbs: Fix crumbs UI for bitbake event class name changes
  bitbake/crumbs: do the test for ignored messages sooner
  bitbake/crumbs: fix the event name determination
  bitbake/goggle: interaction tweaks
  bitbake/depexp: Factor ProgressBar into a separate class in crumbs/
  bitbake/crumbs: add optional pbar parameter to
    RunningBuild.handle_event()
  bitbake/goggle: add a ProgressBar for parse progress
  bitbake/xmlrpc: Modify xmlrpc server to work with Python 2.7
  bitbake/cooker: fix idle command processing in servers
  bitbake/goggle: automatically show most recently added  message

 bitbake/lib/bb/cooker.py                 |    2 +-
 bitbake/lib/bb/server/xmlrpc.py          |   68 +++++++++++++++++++++++++++++-
 bitbake/lib/bb/ui/crumbs/progress.py     |   17 +++++++
 bitbake/lib/bb/ui/crumbs/runningbuild.py |   26 +++++++----
 bitbake/lib/bb/ui/depexp.py              |   19 ++-------
 bitbake/lib/bb/ui/goggle.py              |   15 +++++-
 6 files changed, 117 insertions(+), 30 deletions(-)
 create mode 100644 bitbake/lib/bb/ui/crumbs/progress.py

-- 
1.7.3.2



             reply	other threads:[~2010-12-06 16:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 15:59 Joshua Lock [this message]
2010-11-25 15:15 ` [PATCH 05/10] bitbake/depexp: Factor ProgressBar into a separate class in crumbs/ Joshua Lock
2010-11-25 15:54 ` [PATCH 06/10] bitbake/crumbs: add optional pbar parameter to RunningBuild.handle_event() Joshua Lock
2010-11-25 15:56 ` [PATCH 07/10] bitbake/goggle: add a ProgressBar for parse progress Joshua Lock
2010-12-01 14:40 ` [PATCH 08/10] bitbake/xmlrpc: Modify xmlrpc server to work with Python 2.7 Joshua Lock
2010-12-01 16:59 ` [PATCH 09/10] bitbake/cooker: fix idle command processing in servers Joshua Lock
2010-12-06 15:34 ` [PATCH 10/10] bitbake/goggle: automatically show most recently added message Joshua Lock
2010-12-06 16:11 ` [PATCH 01/10] bitbake/crumbs: Fix crumbs UI for bitbake event class name changes Joshua Lock
2010-12-06 16:11 ` [PATCH 02/10] bitbake/crumbs: do the test for ignored messages sooner Joshua Lock
2010-12-06 16:11 ` [PATCH 03/10] bitbake/crumbs: fix the event name determination Joshua Lock
2010-12-06 16:11 ` [PATCH 04/10] bitbake/goggle: interaction tweaks Joshua Lock
2010-12-07 13:03 ` [PATCH 00/10] BitBake GUI fixes Richard Purdie

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=cover.1291651199.git.josh@linux.intel.com \
    --to=josh@linux.intel.com \
    --cc=poky@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.