Additionally, I would imagine that eventually that "new" API will/should be allot more powerful with extended animation capabilities, integration of new elements [cursor control, opacity, SVG, etc ]. This API is about at it's maximum potential and over the next 6 months will hopefully clean up its act on Macintosh a bit. Doing much more just creates to much code overhead since the base API is so heavy. DynAPI4 won't have this "front-end limitation" so it will be extended in many new and exciting ways. It will also grow and mature as the DOM matures and people add new feature sets. DynAPI4 has allot to offer and allot to get excited about. Why is this important? Because pages built using DynAPI3 will use a "subset" of the future API's capability. This will significantly broaden the options developers have when dealing with clients. 1) Want deep browser compatibility. Fine. But they get a "reduced capability set" so that that particular implementation can/should work in both API3 and API4. 2) Willing to abandon deep browser compatibility. Excellent! Now you get all that DynAPI4 has to deliver with none of the baggage of API3 attached. Eventually, (in 18-24 months) DynAPI3 will just dry up and blow away. But lets let it depart with a little grace. Building in crossover capabilities is not an unmanageable task in my mind. In summary API3 will filter API4 capabilities for clients that desire reverse browser support. You'll do nothing more then what's currently available in this API. DS --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.252 / Virus Database: 125 - Release Date: 5/9/2001 _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dynapi-dev
