>Nothings wrong with backward compatibility.. but there are alot of things
>that can't be done with older browsers (easiest example is trying to do
the
>simplest DHTML trick on an NS3) IE5 for example has some great
image-filters
>that could make kick-ass presentations or other multimedia efforts (i.e.
>games). These things will in NO way work on NS browsers, I know, it's not
a
>"W3C-standard" but it's just an example (even doing something like
>dynamically render contents can be a pain in NS4).
But those features could be in extra libraries, right? Or widgets?
As long as the core is crossbrowser, the extensions could be IE only, or NS
only.
>So we might actually hold back alot of horse power because we can not get
it
>working cross-browser.
In case of Image filters I think Netscape ignores them all together, I used
them
once in a while for creating some cool effects and doesn't even report a
error,
which is perfect for me (I don't have to duplicate the code).
And besides, you can also use DirectX effects in IE (even textures,
polygons,
you name it) which you have to admit open a lot of possibilities, but do you
want
to release something that only Win32 users can see?
>Also where does the back-line end? we already dropped v3.x because of
>logical reasons : no dhtml, but how long can/will/should we support 4.x
>browsers?
When users(and clients, in case of developers) no longer support it,
basically.
As long as they think that DHTML works in 4.x browsers and there's a large
piece
of the market using it (IE 4 is still more used that IE 5.5.)...
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
