Re: Services_Ebay package - maintenance ... or more ?
| From: | Daniel O'Connor | Date: | Sat, 15 Aug 2009 01:19:44 +0000 |
| Subject: | Re: Services_Ebay package - maintenance ... or more ? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-52635@lists.php.net to get a copy of this message | ||
On Sat, Aug 15, 2009 at 5:53 AM, Edouard SWIAC <edouard.swiac@gmail.com>wrote:
> Hello at all the PEAR community!
>
>
> Hereby I would like to propose my help to maintain the package again. But
> after peering at the source code, and experiencing the most common usages
> with the eBay API in my job (basic CRUD most of the time), I think that the
> actual package is a little bit complicated to use and maintain, not to say
> overwhelming.
Can you expand on that with a few examples for us?
When I'm looking at bits like:
http://pear.php.net/manual/en/package.webservices.services-ebay.encoding.php
and
http://pear.php.net/manual/en/package.webservices.services-ebay.example.php
it looks trivial/easy to wrap my head around - ie; I don't see many obvious
bits of bad API.
> So I propose a new version of the package, a less overwhelming version.
> Something very simple that wraps the most used API calls in an efficient way
> (do CRUD with items and orders, following the bids ...). For the rest of the
> calls, an abstract call would be created, allowing the package's user to
> implements easily the calls he needs. Of course the whole package would be
> developped following PHP5 standards with E_STRICT enabled.
>
I think we'd be open to a Services_Ebay_Manager or similar (having the same
kind of relationship to Services_Ebay that HTTP_Client has to HTTP_Request)
>
> I don't know if it's in the PEAR philosophy to rewrite a package instead of
> just update its code. Nonetheless, I hope the community shall consider my
> request as it is very serious, while being very important for me on a
> personnal level since it would be my first steps in an official PHP
> developpers' community.
>
Oh, we're not too picky about it.
Sing out when you get code samples you'd like to share!