<?xml version='1.0' encoding='ISO-8859-1'?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-5144379</id><updated>2008-09-26T16:38:41.594+01:00</updated><title type='text'>Peter Brett's Blog</title><subtitle type='html'>Peter Brett's website news, random thoughts and articles on space technology...</subtitle><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default?start-index=26&amp;max-results=25'/><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://peter-b.co.uk/blog/atom.xml'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>201</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-5144379.post-4195316456756393287</id><published>2008-09-21T18:17:00.002+01:00</published><updated>2008-09-26T16:38:41.614+01:00</updated><title type='text'>More cooking escapades</title><summary type='text'>

I tried out two recipes yesterday, with lots of success (well, I
  thought so, anyway).

First was nice and simple recipe
  for lemon
  drizzle cake from the BBC Good Food website -- I used it as a
  fallback plan when I failed to obtain a copy of my mother's
  legendary and delicious recipe.
I made it in a 20 cm spring-form tin instead of a loaf tin as
  the recipe suggests (I don't have a </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=4195316456756393287' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/4195316456756393287'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/4195316456756393287'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2008/09/more-cooking-escapades.html' title='More cooking escapades'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-1940635004164709314</id><published>2008-06-25T19:05:00.001+01:00</published><updated>2008-06-25T19:05:36.742+01:00</updated><title type='text'>Emacs word counting and tab completion</title><summary type='text'>
    

I've been doing a lot of work that's required me to keep an eye on
word counts recently, so I've needed a decent word count function in
Emacs. The easiest way to implement this was to use the wc
command from CNU coreutils.


(defun word-count nil "Count words in buffer" (interactive)
  (let ((start (if mark-active (point) (point-min)))
        (end (if mark-active (mark) (point-max))))
</summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=1940635004164709314' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/1940635004164709314'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/1940635004164709314'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2008/06/emacs-word-counting-and-tab-completion.html' title='Emacs word counting and tab completion'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-3944953829824915917</id><published>2007-12-25T18:26:00.000Z</published><updated>2007-12-28T20:40:27.072Z</updated><title type='text'>Christmas</title><summary type='text'>Having been horribly ill for what feels like most of December, Christmas is now here!  I'm spending Christmas with my parents and all of my siblings, and it seems like I've been running around like a mad things for the last few days getting everything clean, tidy and ready for Christmas.  On Christmas Eve my mother and I were at the butchers' shop at half past six in the morning to get the turkey</summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=3944953829824915917' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/3944953829824915917'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/3944953829824915917'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/12/christmas.html' title='Christmas'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-1911844716285650013</id><published>2007-12-07T23:06:00.001Z</published><updated>2007-12-07T23:06:51.648Z</updated><title type='text'>Error-reporting progress</title><summary type='text'>
    

Further to
my previous
blog post on error-reporting in libgeda, I've made some pretty
good progress on implementing the ideas that I described.  In
  particular:

  The file opening functions (f_open()
    and f_open_flags) now use GError to return error
    messages rather than just spewing them to the console.
  gschem now shows an informative dialog box when it fails to load
    a file.</summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=1911844716285650013' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/1911844716285650013'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/1911844716285650013'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/12/error-reporting-progress.html' title='Error-reporting progress'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-3738011513328158292</id><published>2007-11-27T23:22:00.001Z</published><updated>2007-11-27T23:22:32.481Z</updated><title type='text'>Error reporting &amp; handling in libgeda</title><summary type='text'>
    

Apparently some people do read my blog: Peter Clifton and I met up
  for a drink at Borders in town this evening, and he recommended that
  I write more often.  So here's this evening's contribution, on a
  slight refactor of libgeda error reporting.

It's been a while since I last blogged about gEDA development, and
  since then I've had the good fortune to be able to travel to
  </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=3738011513328158292' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/3738011513328158292'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/3738011513328158292'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/11/error-reporting-handling-in-libgeda.html' title='Error reporting &amp;amp; handling in libgeda'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-310835385305455939</id><published>2007-07-23T18:12:00.001+01:00</published><updated>2007-07-23T18:12:17.891+01:00</updated><title type='text'>Taking time out</title><summary type='text'>
    
Much of my work on gEDA recently has met with rather mixed
  responses, many not particularly positive.  Most of the things that
  bug me are fixed, so between the lukewarm reception that seems to
  meet my changes and the absence of any particular itch to scratch,
  I'm taking a little time out from gEDA hacking.  This will also
  (hopefully) help with my RSI, which is slightly more </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=310835385305455939' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/310835385305455939'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/310835385305455939'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/07/taking-time-out.html' title='Taking time out'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-1308010033700875820</id><published>2007-06-30T14:59:00.001+01:00</published><updated>2007-06-30T14:59:31.667+01:00</updated><title type='text'>Making embedding more useful</title><summary type='text'>
    

One of the trickiest problems electronic engineers have is with
  keeping their symbol libraries up-to-date while not breaking old
  schematics (e.g. with changing pin positions).

Currently, most people use one of two approaches to managing the
  problem:


  gEDA has the ability to embed symbol data in the schematic file,
  making the schematic independent of changing symbol libraries, </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=1308010033700875820' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/1308010033700875820'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/1308010033700875820'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/06/making-embedding-more-useful.html' title='Making embedding more useful'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-3517568688629922262</id><published>2007-06-30T12:21:00.001+01:00</published><updated>2007-06-30T12:21:30.668+01:00</updated><title type='text'>Terminal emulators, utmp and setgid</title><summary type='text'>
    

Something that's been really irritating me recently on major Linux
  distributions is the increasing proportion of user software being
  installed setgid.

This is usually for security reasons; for instance, to either
  protect system services from accidental user interference, or to
  protect the user's personal information from being sniffed by other
  software they may be running.

</summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=3517568688629922262' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/3517568688629922262'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/3517568688629922262'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/06/terminal-emulators-utmp-and-setgid.html' title='Terminal emulators, utmp and setgid'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-2505300823794929626</id><published>2007-06-29T13:40:00.001+01:00</published><updated>2007-06-29T13:46:51.038+01:00</updated><title type='text'>Hacking in the unstable branch</title><summary type='text'>

For most of June, gEDA has been in the process of switching from
  using CVS to git for version control, and quite a lot of developers'
  time seems to have been spent on getting used to the new system.  I
  really like the new system; it makes reviewing changes and 
  maintaining patchsets so much less of a chore, and my productivity
  has gone through the roof!

I've made really good progress</summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=2505300823794929626' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/2505300823794929626'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/2505300823794929626'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/06/hacking-in-unstable-branch.html' title='Hacking in the unstable branch'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-7826951945525489220</id><published>2007-06-02T23:49:00.001+01:00</published><updated>2007-06-02T23:49:34.660+01:00</updated><title type='text'>gEDA is moving to using git</title><summary type='text'>
    
A few days ago in response to other developer's comments/complaints
  on moving gEDA to using Guile 1.8, I suggested forking a stable
  branch of gEDA which would use Guile 1.6 while keeping the main
  development tree using Guile 1.8.
Ales decided this was a good idea, saying:
Here's the plan going forward:
  
    I do want a stable/unstable branch/release arrangement going
      forward.
</summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=7826951945525489220' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/7826951945525489220'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/7826951945525489220'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/06/geda-is-moving-to-using-git.html' title='gEDA is moving to using git'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-2224112739906816028</id><published>2007-06-01T23:13:00.001+01:00</published><updated>2007-06-08T21:57:58.721+01:00</updated><title type='text'>Abject failure to install Fedora 7</title><summary type='text'>
    
I was very excited about the release
  of Fedora 7 yesterday,
  as I've been a loyal Fedora user since Fedora Core 3 was released
  back in 2004.
You'll notice my use of the past tense.  This is because I spent
  most of today trying to get Fedora 7 to install.  I'm extremely glad
  I took a full backup of my files, as my various attempts to get the
  installer to run without crashing hosed</summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=2224112739906816028' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/2224112739906816028'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/2224112739906816028'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/06/abject-failure-to-install-fedora-7.html' title='Abject failure to install Fedora 7'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-7429082703170958599</id><published>2007-05-29T22:38:00.001+01:00</published><updated>2007-05-29T22:38:07.871+01:00</updated><title type='text'>New library system now in CVS</title><summary type='text'>
    
After the SEUL server move was successfully completed, Ales
  released a new snapshot of gaf.  With that out of the way I was
  given the all clear to merge my component library work.
I've therefore nuked the "libraries" branch from my
  public git repository, as it was no longer relevant.
There are a number of things I want to get sorted out before the
  next release (which is likely to be</summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=7429082703170958599' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/7429082703170958599'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/7429082703170958599'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/05/new-library-system-now-in-cvs.html' title='New library system now in CVS'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-3388344466261677017</id><published>2007-05-24T21:53:00.001+01:00</published><updated>2007-05-24T21:54:52.983+01:00</updated><title type='text'>Chocolate Birthday Cake</title><summary type='text'>
    
We made a rather delicious birthday cake for one of our friends,
  and it worked so well I thought I'd post it here (because I'm bound
  to lose the piece of scrap paper it's scribbled on).
For the cake

6 oz butter
6 oz caster sugar
3 eggs
8 oz plain white flour
3.5 tsp baking powder
3 tbsp cocoa powder

Preheat oven 180° C. Whisk eggs.  Cream butter and sugar
  together.  Sift in flour </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=3388344466261677017' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/3388344466261677017'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/3388344466261677017'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/05/chocolate-birthday-cake.html' title='Chocolate Birthday Cake'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-3990256569474742642</id><published>2007-05-23T20:17:00.001+01:00</published><updated>2007-05-23T20:17:21.546+01:00</updated><title type='text'>Website updates and component library work</title><summary type='text'>
    
In order to put (much) more information about my gEDA work on my
  website, there's been a slight reorganization; I've made a new
  section for "software" in which I've put a
  whole page on gEDA development.
  It contains more information on my git repositories and the tools I
  use.
I've also put a list of things I've been working on recently, and a
  list of things I've got planned.
I've</summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=3990256569474742642' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/3990256569474742642'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/3990256569474742642'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/05/website-updates-and-component-library.html' title='Website updates and component library work'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-7160810240196914619</id><published>2007-05-21T07:30:00.001+01:00</published><updated>2007-05-21T07:36:31.765+01:00</updated><title type='text'>Better blogging with Emacs</title><summary type='text'>
    
Having got Emacs 22 set up
  with g-client
  I rapidly got annoyed with the necessity of continually copying and
  pasting URLs from a web browser window in order to post to my blog
  and to page through the posts available, so I quickly hacked
  together some ELisp to make it easier:
;;; Blogger support
(add-to-list 'load-path "~/.emacs.d/site-lisp/g-client")
(load-library "g")
(setq </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=7160810240196914619' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/7160810240196914619'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/7160810240196914619'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/05/better-blogging-with-emacs.html' title='Better blogging with Emacs'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-1563888301365064986</id><published>2007-05-20T09:02:00.000+01:00</published><updated>2007-05-20T09:03:07.784+01:00</updated><title type='text'>Tab-completion in Emacs' c-mode</title><summary type='text'>For a long time, I've wanted tab-completion in Emacs when
  programming in C, and haven't had the time to delve into ELisp
  enough to work out how to do it.  However, thanks to
  the Emacs Wiki I now have it
  working!
I added the following to my .emacs file:

; Better tab completion
(defun indent-or-complete ()
  "Complete if point is at end of a word, otherwise indent line."
  (interactive)
  </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=1563888301365064986' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/1563888301365064986'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/1563888301365064986'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/05/tab-completion-in-emacs-c-mode.html' title='Tab-completion in Emacs&apos; c-mode'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-8081572360670949437</id><published>2007-05-20T06:57:00.001+01:00</published><updated>2007-05-20T09:05:25.126+01:00</updated><title type='text'>Blogger annoyances and Emacs 22</title><summary type='text'>When I set up my weblog
 on Blogger I made the error of
 enabling an option which caused all newline characters in my
 postings to be converted to literal HTML newlines
 (&lt;br&gt;).  This was fine for a long time, until I
 wanted to write my blog postings in a text editor with HTML support
 (such as Emacs) and
 then copy them into my weblog.  Emacs has really good support for
 general text editing </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=8081572360670949437' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/8081572360670949437'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/8081572360670949437'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/05/blogger-annoyances-and-emacs-22.html' title='Blogger annoyances and Emacs 22'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-8140548263296877797</id><published>2007-05-19T12:52:00.001+01:00</published><updated>2007-05-20T14:54:39.933+01:00</updated><title type='text'>New component library for gEDA</title><summary type='text'>     
     
Rather than revising for my exams, I've been rewriting
  the gEDA component library
  system.  The motivation was to provide a way to use the output of
  arbitrary commands as symbols in your schematic, and to have a way
  for code in gEDA applications to find and use schematic symbols
  without caring about where they're coming from.
My new all-singing all-dancing code is now in a </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=8140548263296877797' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/8140548263296877797'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/8140548263296877797'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/05/new-component-library-for-geda.html' title='New component library for gEDA'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-4345919054032536015</id><published>2007-04-23T17:39:00.000+01:00</published><updated>2007-04-23T17:52:41.560+01:00</updated><title type='text'>Farewell, TWU</title><summary type='text'>Sadly, I've had to move away from TWU, where my site had been hosted for several years, after e-mail services disappeared for a day without warning.  The change had been looming for a while, given TWU's movment away from hosting towards consulting; indeed, the fact that I hadn't been even able to get in touch with the admins to pay them for my hosting for more than a year had been a major </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=4345919054032536015' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/4345919054032536015'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/4345919054032536015'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2007/04/farewell-twu.html' title='Farewell, TWU'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-115701969521861205</id><published>2006-08-31T11:15:00.000+01:00</published><updated>2006-12-18T23:56:41.233Z</updated><title type='text'>Brush Primitives</title><summary type='text'>Someone contacted me this morning asking about the Brush Primitives texture format.  So since the q2bsp wiki was down, I dug out some very old-fashioned paper notes I'd made a few months ago, dusted them off and turned them into a PDF using LyX.  Ah, nothing like TeX for typesetting mathematics.In other news, we were planning to launch rockets this morning, but there was some sort of pony camp </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=115701969521861205' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/115701969521861205'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/115701969521861205'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2006/08/brush-primitives.html' title='Brush Primitives'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-115607795693470307</id><published>2006-08-20T12:18:00.000+01:00</published><updated>2006-12-18T23:56:58.176Z</updated><title type='text'>Launch postponed</title><summary type='text'>Although we did successfully build a two-stage rocket last week, we've had to postpone launching it until next weekend.  Not only has it been raining on and off for the whole of this weekend, but being unable to find a suitable launch site and the lack of transport didn't get resolved in time.  Hopefully our luck will change soon!</summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=115607795693470307' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/115607795693470307'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/115607795693470307'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2006/08/launch-postponed.html' title='Launch postponed'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-115559310945342575</id><published>2006-08-14T21:37:00.000+01:00</published><updated>2006-12-18T23:57:26.640Z</updated><title type='text'>Molten parachute</title><summary type='text'>Well, mid-afternoon on Sunday the weather cleared up long enough for us all to head down to Midsummer Common and launch our rockets.  We had two to launch: Mike's, and mine.  A couple of other folks from the lab turned up to help, including our 'propulsion expert', Henry.After improvising some drinking straws and a few wooden skewers into a 'launch pad', assembling the motors into the rockets and</summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=115559310945342575' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/115559310945342575'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/115559310945342575'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2006/08/molten-parachute.html' title='Molten parachute'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-115545462405260334</id><published>2006-08-13T08:32:00.000+01:00</published><updated>2006-08-13T08:37:04.063+01:00</updated><title type='text'>Rainy season</title><summary type='text'>Just when I needed still, sunny weather to launch a rocket, the clouds opened: it's been raining more or less non-stop for the whole weekend so far.  So I've been stuck indoors playing Red Orchestra and The Ocarina of Time.  mupen64 is a great project!  Unfortunately it only supports x86 systems, so I've had to run it under Windows (this is probably a good thing, considering that its Direct3D </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=115545462405260334' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/115545462405260334'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/115545462405260334'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2006/08/rainy-season.html' title='Rainy season'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-115524375663831410</id><published>2006-08-10T20:59:00.000+01:00</published><updated>2006-08-15T22:42:08.796+01:00</updated><title type='text'>Model rockets</title><summary type='text'>Gosh, I haven't posted anything for a very long time (and this isn't the first time I've neglected this blog).  But an awful lot of things have been happening!I spent most of the summer term working quite hard, and it paid off: I got a II.1 in my part IA exams, and I was only 1% off a First!  If I hadn't spent so long playing GTA San Andreas when I should have been revising, I might have got that</summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=115524375663831410' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/115524375663831410'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/115524375663831410'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2006/08/model-rockets.html' title='Model rockets'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry><entry><id>tag:blogger.com,1999:blog-5144379.post-114643747403357783</id><published>2006-04-30T23:37:00.000+01:00</published><updated>2007-05-19T15:28:21.201+01:00</updated><title type='text'>Portability games</title><summary type='text'>I found out why the sky wasn't working: it turns out that q2bsp (the new name for qbsp3) gets the flags that tell it if a face is part of the skybox by reading the headers of the texture files. It wasn't able to load the textures, so it couldn't work out that the sky-textured bits were actually sky.

One thing led to another, and I ended up rewriting not only the PAK loader, but just about all </summary><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=5144379&amp;postID=114643747403357783' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/114643747403357783'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5144379/posts/default/114643747403357783'/><link rel='alternate' type='text/html' href='http://www.peter-b.co.uk/blog/2006/04/portability-games.html' title='Portability games'/><author><name>Peter</name><uri>http://www.blogger.com/profile/13507691713687465296</uri><email>noreply@blogger.com</email></author></entry></feed>