I'm really enjoying the discussion this thread is producing, but it
seems to me that, at this point, splitting the API up by browser
shouldn't be a priority. I agree that the benefits of splitting are
minimal at this point and would require lots of careful maintenance that
a lot of people won't bother to do.
I don't think imposing tight restrictions on development is really true
to the spirit of this API. Once we decide to have official requirements
-- whether it be splitting, an "official" widget model or inheritance
scheme -- then we'll also have to have to impose rules so that people
won't doing things that will break our precious standard. The only
thing that should be standard for now is the core. Everything else can
be done however you want to. If you wanted, you can do as Pascal did
and use the DynAPI2 source to build in whatever modifications you
desired.
That doesn't mean that we won't do it in the future, though.
--
scott andrew lepera
-----------------------------------
web stuff: www.scottandrew.com
music stuff: www.walkingbirds.com
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
