On 03/23/2013 08:50 PM, DAVID HODGKINSON wrote:
Are there any tutorial type docs for Moose Meta the way you used it or
which man page should I be able to work it out from?
Perhaps a course...
http://perlschool.co.uk/courses/object-oriented-programming-with-perl-and-moose/
:-)
Dave...
--
Message: 1
Date: Sun, 24 Mar 2013 09:59:37 +
From: Dave Cross d...@dave.org.uk
Subject: Re: API wrapper best practices?
To: london.pm@london.pm.org
Message-ID: 514ece89.1070...@dave.org.uk
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 03/23/2013 08:50 PM, DAVID
On 24 March 2013 14:13, Ashley Hindmarsh ash+p...@best-scarper.co.uk wrote:
I guess the holy grail is something that takes the API schema and builds
the classes on-the-fly
I don't know about holy grails but there's SPORE [0] which lets you
describe RESTful APIs and automatically generate
On 03/24/2013 01:13 PM, Ashley Hindmarsh wrote:
Actually I was about to point at something Moose-y that exercises a public
API, such as DC's Net::Songkick.
I was playing with this last year, and it's nice, but you always feel that
you shouldn't need to roll your own classes.
Yeah. While
On 24 Mar 2013, at 13:13, Ashley Hindmarsh ash+p...@best-scarper.co.uk wrote:
I guess the holy grail is something that takes the API schema and builds
the classes on-the-fly, and is closer to what Dave Hodg is after.
People thought of that, and now we have SOAP. So be careful for what you wish
And now we have SOAP??? For me _at least_ SOAP came first
On Sun, Mar 24, 2013 at 9:04 PM, Sam Kington s...@illuminated.co.uk wrote:
On 24 Mar 2013, at 13:13, Ashley Hindmarsh ash+p...@best-scarper.co.uk
wrote:
I guess the holy grail is something that takes the API schema and builds
the
