Re: Comments on SVG 1.2 from a Gecko developer

>
>
>> Java:
>>     DOMWindow w = document.getWindow();
>>     SVGWindow w2 = (SVGWindow)w;
>>     Connection c = w2.createConnection();
>
>Surely the real problem here is that Java already has networking
>APIs.  This feature is not a Document Object Model feature; it
>is a viewing platform object model feature, and it is largely
>premised on the idea that there is only one language binding
>that matters: ECMAScript (commonly called JavaScript) - i.e.
>SVG describes an application platform, and that platform uses
>ECMAScript - it no longer describes a document language.
>
It has nothing to do with whether Java already has networking APIs. The 
problem here is that Java uses a static type system which often requires 
you to name the interfaces you are using. You can avoid the problem by 
saying that such languages may not use these potentially migrating APIs, 
or simply that these APIs are only accessible by ECMAScript, but you'd 
better say so in the SVG 1.2 spec.

Rob

-- 
Robert O'Callahan <robert@ocallahan.org>
"In the beginning was the Word, and the Word was with God, and the Word
was God. ... The Word became flesh and made his dwelling among us. We
have seen his glory, the glory of the One and Only, who came from the
Father, full of grace and truth." 1 John 1:1,14

Received on Friday, 9 July 2004 12:35:04 UTC