> Additionally, I think the base API should focus on "staying lean and mean"
> and solving some fundamental problems. That being:
>
> 1) Memory Issues (API and Widget) - This needs a focused effort as it is
> probably the greatest handicap this API has right now.
> 2) Documentation and Instruction - Linked to (1), we may have
> improved the
> base API for memory but widgets need a structured approach so they can be
> built "memory safe" as possible.
> 3) At a minimum get the current API at least to the point of the
> prior with
> at least "ONE" workable solution for the Macintosh. Netscape 4
> was hosed by
> the last release.
I think the above are the issues we should really be focussing on here.
Particularly the fact that the API doesn't work on a Mac anymore. That's a
big let down for the Mac community, and would turn a lot of developers away
from using the API. Documentation in my mind is also a biggie.
In saying that, I don't have a Mac to try and fix things on, and I suspect
neither do any of the core developers.
I know it's more interesting playing around with server-side extensions, but
there are some really basic requirements that the API currently does not
meet, like being cross platform.
Cameron.
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
