bgeek.net

Featured

OAuth MVC.net Revisited

Posted by Owen Evans on Tuesday, March 3rd, 2009

My Foray into OAuth with MVC.net is getting more thorough. I quickly came upon a problem in the project as it stood with regards to the signing methods I’d used.

I’d grabbed the OAuth base class from the samples available over on oauth.net but quickly found out (well actually not that quickly, I still had to [...]

Back out of black

Posted by Owen Evans on Monday, February 23rd, 2009

The controversial (to say the lease) piece of rubbish legislation that is Section 92A has been delayed by parliament due somewhat to the presure we put on government through protests etc.

It’s not over but this is the first sign that anyone’s actually listening.

More here Sphere: Related Content

Added a sample OAuth consumer in Cocoa

Posted by Owen Evans on Saturday, February 21st, 2009

Well this is my first foray into the world of objective-c programming, but I’ve added a sample consumer for mac os x to the ms-mvc OAuth project, I know it’s not mvc specific (I’m going to write an mvc consumer next) but as I program on my Mac it was useful for me to have [...]

Is that you?

Posted by Owen Evans on Friday, July 18th, 2008

I didn’t recognise you it’s been so long.

I finally got the urge and the patience to fire up my editor and write a post for this long neglected weblog.

How are you all doing? good I hope?

Ok so I may have been prompted to write by a link from Julian over at ProWorkflow but I’m here now and that’s all that matters, isn’t it?

But what to write about? That’s one reason I’ve not posted an update for so long, I’ve been keeping my head down getting as much done at Xero as possible, and not really coming up for air.

So a couple of posts that I’ve been meaning to write and never got around to:0

Email and the myth of standards (or how I created a chain of 3000 emails in an hour),
How to keep your eye on the goal and not be distracted by the shiny fruit of extra features
Why estimation is sooo hard
Why estimates are so useful

For now I’m going to be terse and keep things concise.

Open Question: What makes a good API?

So you’ve got a product that loads of people could potentially tap into the use of if only there was a clear and concise way of tying in their existing product line into yours. So you need an API, but an API is useless unless people actually use it.

economizing,Electrical Component,Power Line,Electricity,Concepts,Technology,Alternative Energy,Efficiency,Single Object,Cable,Clip Art,Web Button,Smooth,Colour,Illustration and Painting,Design Element,Symbol,Sign,Web 2 0,Two Pin Plug,Label,Isolated On White,Simplicity,Environmental Conservation,Green,Gradient,Shadow,White,Energy,Electrical Plug At the moment Xero has a functional and useful API that’s available to our many Network partners , we love the idea that people can do many of the great features that we can’t get round to right now (and I’m not sure we’d want to). Easy accounting is our goal and allowing you to use the solution for Payroll or Project management that suits you and get as much generated in Xero as possible really suits us down to the ground.

But an API is only as good as the tools that use it, and we rely on development effort to get the external products working well with Xero, we’ve tried to make the API as clean as possible, but we really need feedback.

What do you want from an API? What makes an API easy to use for you?

Interested in feedback.

This is not a Xero mandated survey, I’m just interested in what people think about API’s and what makes them good.

Sphere: Related Content

Posted in: [questions|xero|xero api].