> (2) Lets face it, IE is rapidly approaching ubiquitous levels. In
addition
> to baseline DOM support MicroGreed also adds a series of "proprietary
> extensions". The API's extension would be a great place to explore
> expanding the "base" API into IE-centric add-ons (most of these can
actually
> be built into CSS formats to shield them from unsupported browser. I'm
> prepared for Spam on this issue, but my opinion is that this API should
> "seek" to represent both a stable-core and the ability to deliver the
> "state-of-the-art".
The distro should never, ever, contain IE specific extensions. The
whole point of the DynAPI is cross-browser. If you want IE
extensions, then you can provide them separately.
Totally agree on this, hence it would be located in "DynAPI extensions",
which should have a second domain on Source Forge separate from DynAPI core.
I will say that the definition of an API could and should be "the ability to
deliver a common baseline cross-browser experience with the integrated
ability to extend into a higher art based on browser specific conventions,
it's called scalability". The later doesn't harm the prior and the sum
total is greater from a capabilities standpoint.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.250 / Virus Database: 123 - Release Date: 4/18/2001
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
