Alan D. Cabrera wrote:
It's been over a month since this discussion started. It seems like
we have some core consensus on a lot of things. So, I was curious
about how we should proceed. I'm not sure how this community usually
proceeds so I'll just toss out an idea.
Good start...
I thought that Mike had a made good start with a seed API. I was
thinking that it would be cool we put it in the sandbox or trunk,
which I think is going to be the 2.0 release. Everyone with a use
case can start coding them with the idea that they would become
examples put into an examples module. This would kill two birds with
one stone. We get a feel for how the API codes and we get nice
examples for users to look at.
The whole idea is for the API to initially be an empty mock API for us
to code the examples against. This shouldn't be too hard to do since
I think the bulk of the API so far is interfaces.
I think this is a great idea, Alan. I'm definitely up for giving a mock
client API a spin drive.
-timothy
