[Dynapi-Dev] Browser support branching...

[Joy Ride]

Hello,

There has been some discussion about how browser support for DynAPI3 should be branched. We would use the "sum of largest common" -method for that. Based on our tests and knowledge base branching would look like this (some of you have allready suggested similar tree to ours):

Common
|
|__DOM
| |
| |__MSIE5/6
| | |
| | |__MAC
| | |
| | |__PC
| |
| |__NS6/7
| | |
| | |__PC
| | |
| | |__Linux/MAC***
| |
| |__Opera 7*/****
| |
| |__Mozilla*/****
|
|__NS4
|
|__MSIE4
|
|__Opera5/6
|
|__PocketPC MSIE 2002**

Some explanations
* It maybe possible to combine this branch with NS6/7 branch
** Needs more consideration and documentation before it can be decided if it's possible to support Pocket PC MSIE, basically Pocket PC MSIE 2002 is MSIE5 without some features
*** There maybe need to separate MAC and Linux branches, they are prety close to each other, but there may be some differences
**** At this point we do not have information if these browsers need separate platform branches to be fully supported.

By branching I do not mean that everything should be coded for each branch. Just the parts, which do need either optimization or extran compability. In our opinion this way we could create the maximun set of features for each browser and optimize the performance for each browser enough.

What do you think about this approach?


- Juho Risku

_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/