Current goals as I understand them:
 
1) Fix all know bugs in IE 4.x &5.x and NS 4.x on PC and MAC (linux?)
2) Ensure that all code works (consistantly) with IE 4.x &5.x and NS 4.x on PC and MAC (linux?)
3) Implement WC3 DOM support using NS6 as a test basis
 
4) and THEN we tackle improving size and speed
5) release "official" DynAPI 2.0 FINAL version.
6) figure out what we do for our next trick.
 
Doug Melvin
 
Please excuse my previous rants if they hurt yer head alittle, I'm a very big bitch without my coffe
(had coffe x2.. fell much better now.. :-)  )
----- Original Message -----
Sent: Monday, March 12, 2001 1:02 PM
Subject: [Dynapi-Dev] Re: [ dynapi-Patches-407882 ] Browser.js Recommended Upgrade

From looking at the code that is in the current browser.js file we attempt to
do at least 2 things:

1.  identify the browser
2.  identify the platform

Here are the problems that I see.  We only support MSIE or NS, so why do
allow for browsers that spoof, such as Opera, to get by?  Why not explicity
detect them so that we can alert that they are not supported?  When we
attempt to detect the platform we are using methods that are almost
guaranteed to fail.

I'm not saying that the entire thing should be included, but at the least
shouldn't we fix the most obvious problems which have an effect on the way in
which the DynAPI works?

BTW, since I can't seem to find a list of the CURRENT GOALS, can someone post
them to the list for me.  I would like to learn more about them and see what
can be done to meet them before the future becomes the past and we get stuck
in the present.
 

---
Outgoing mail is certified Virus Free by AVG Free Edition
Download at: http://www.grisoft.com/html/us_index.cfm
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.237 / Virus Database: 115 - Release Date: 3/7/01

Reply via email to