Our Wedding – Part Three

Continued from Our Wedding and Our Wedding – Part Two.

Leg of Lamb

I was most impressed by the way the Manor staff brought out everyone’s main course at once. I’m not sure what size oven they’ve got, but they managed to produce 65-ish sizable legs of lamb all at the same time.

The food was the main reason we chose this place. We wanted to make sure people were well fed, as it’s so common to find yourself with a cheesey canapé trying to last you for the whole day.

The main wedding meal is called the Wedding Breakfast. This is ridiculous. Continue reading Our Wedding – Part Three

Tired of ME

This post is a follow-up to All About ME.

I have been planning to write another post, about what it’s like on a day-to-day basis without any episodes, but 2 weeks ago or so, I felt tired again.
It’s got worse, and I’m now off work (something I really try hard to avoid). I’d write something about how it feels, but I’m knackered, my hands are shaking, I can’t concentrate.
Going to see the doctor at 8.45am tomorrow.
Currently drifting about the house, wanting to do useful things, but completely incapable. Arg.

I’ll try and mentally write a good post about it ready for when I can type it up.

Our Wedding

On June 12th last year, nearly 18 months after we first met on the tube, I asked Agnieszka to marry me. During a private dinner for two on a beach in Mexico, I asked the waiter to give us 10 minutes, dropped to one knee and dug out the ring I’d been hiding away with me since I’d popped into Tiffany’s on my 30th birthday three weeks beforehand. She said yes almost before I’d finished the question.

It took two weeks after our return to London for a brochure to land on our doormat. Agnieszka had been to Bradenham Manor before, and two things quickly became clear: that this would be our perfect reception venue, and secondly, that this would not be the longest engagement.
The most complicated arrangement turned out to be the church. Continue reading Our Wedding

app-engine-patch and custom users

You can use your own user object with app-engine patch:
http://code.google.com/p/app-engine-patch/wiki/CustomUserModel
Very clever. So it’s kindof one of things you do early, because you don’t want to switch user models later.
Trouble is, once you’ve switched models, and fixed any missing-field issues, you have wiped your users away, and can’t login!
Can be a bit embarrassing as a rookie, and the Django peeps seem generally unforgiving to anyone who hasn’t memorized the book, website and IRC conversations back to 1997.

Here’s the fix:
Go to the app engine datastore console:
http://localhost:8000/_ah/admin/interactive
In the Interactive Console do this:

from google.appengine.api import users
from django.contrib.auth.models import User
u = User(username='admin', password='admin', email='email@example.com')
u.set_password('admin')
u.put()

You can then head to the forms in the Datastore Viewer to tweak further. Set is_staff and is_superuser flags on.
Now you can login as admin/admin as before.

Fireworks in Flex – Faster and with Source!

I’ve cleaned out the Fireworks code – it’s fast. Not smooth though – I don’t know how to do a proper timer in Flex – anyone got any hints over how to be smoother than just running off the frame event?
Anyway, source is here, for your hacking pleasure. There’s a txt file to explain what you need inside.
Demo:http://js-fireworks.appspot.com/flex/index.html
Source:http://js-fireworks.appspot.com/flex/flex.zip

For the record, I still prefer the JavaScript version 🙂

Porting JS-Fireworks to Flash

Flash ActionScript is pretty much JavaScript right?
So, I thought my Chrome Experiment, js-fireworks should be trivial to port across to AS, and take advantage of the extra speed.
It did prove pretty simple.
Instead of a canvas, I create a Sprite. The Sprite has a graphics object which is usable in much the same way as the canvas. So all I needed to do was to switch the methods around a bit and voila!
One gotcha was the difference in calling setTimeout, which does not pick up the right context. When I call FireworkDisplay.blah, it should have the context of FireworkDisplay, not global.
Second gotcha was the redefinition of loop variables. This is illegal:

for (var i=0;i<20;i++) { } for (var i=0;i<20;i++) { }

I think this is a flaw in Flash. The var declares the loop counter to be local to the loop, so it should not "keep" a definition after exiting the loop. It's a pain.
Finally, the colours are a bit off. Don't know why - I pinched a simple util to convert rgb to hex, and I think it's off.
Anyway, it works. No extra speed though. Will have to look at optimization later.
Click here to see the demo.
Or click here to download the source.