I’ve played with ways that CurrentCost users could compare their usage with their friends for a while.
But now I want to see how it will cope with a bigger group of users.
Want to join in? I’ve started writing some instructions – please do give it a try!
Update: I figure that if I’m asking for people to help me, then it’s only fair that I give something back. So I’ve made available the Python source that reads and parses CurrentCost updates.
It was my wife’s birthday last week. As a part of the birthday present that our three year old, Grace, made for her, I made a font based on Grace’s handwriting.
This isn’t terribly technical, or even new. But I thought it was cute. 🙂
Between holidays, meetings, work and other stuff, I put CurrentCost stuff to one side for a few weeks.
I’m back now, and thought I’d share my plans for the app. If nothing else, I figure it’s useful for me to refresh my memory and plan my next step!
I’ve had a Treo Pro for a couple of weeks now so I thought I’d write a post about what I think of it.
If you’re the sort who likes to skip to the end of stories, let me save you a little time. I’m loving it. It’s awesome.
I’ll try and explain why in this post.
This one has been bugging me for a few days, and with help from a very helpful Google engineer I’ve finally got this working, so I thought I’d share my code where the next poor soul to try and do it might find it!
The problem:
I’ve written a small web service which I am hosting on Google App Engine.
By adding “login: required” to specific services in the app’s app.yaml file, I can make sure that you need to login to access a service.
If you’re accessing the service from a web browser, this is fine – you get redirected to a Google login page, and after entering your username and password and hitting ‘submit’, you get sent on to the web service you wanted.
But how do you do that programmatically? I wanted to do it from a Python application on my desktop, without being able to navigate the HTML login form.
It’s been a very geeky week – only a couple of days after BathCamp, I was in London yesterday for Google Developer Day.
I was saying only a couple of days ago that I really need to get my head around some of the options out there for web developers, so this was well timed.
I learnt about web development tools and online APIs, talked a lot about where mobile development is going, and got to wander around Wembley Stadium. All in all, it was a good day. 🙂
The underlying theme for the talks throughout the day was showing how Google are trying to make the web ‘better’.
The messages were grouped into four key areas:
I made a ton of notes throughout the day. Rather than write the world’s longest blog post, I’ve picked out a few interesting bits.