[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2004-07-23, Elias Pschernig <elias@xxxxxxxxxx> wrote:
> Yes, I was already browsing through http://alleg.sf.net/future/
> before, and a lot of things could go in. [...] I also discovered
> there a completely prefixed A4 API by Grzegorz, something which
> I'd apply at once.
Don't. API is possibly the last thing which should go in. While
it is nice to have a good guide to start with, much effort goes
into hot air and not code. Just look at the AllegroPro naming
threads. Imagine having that for each symbol of the library.
Besides, I have read that again and found many inconsistencies,
so it's not a good guide. Maybe I should remove that junk to avoid
polluting any future discussion.
My idea now of making a good API for Grozilla (or whatever lib with
a nice user base) would be to get 90% of the lib itself working. Then
pick three of the guys who wrote it to discuss the naming of symbols
*in private*. Shouldn't take long. When they release their version,
take 20 developers and tell them to convert their old sources to
this new API. If possible, do this step also *in private*. After
their result, get feedback on how they find the API. If necessary,
modify the API and do a second round with another *different*
20 developers. After this, release the API in public. The whole
process shouldn't take longer than writting the last 10% of the lib.
In private means people don't go and post the whole API on the
mailing list or the web forums, that would spoil the quality of
later feedback.