W3C home > Mailing lists > Public > www-svg@w3.org > December 2004

Re: LC Comment - Script & Progressive Rendering / Multiple Pages

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Wed, 01 Dec 2004 14:31:38 -0600
Message-ID: <41AE2A2A.2070709@mit.edu>
To: Peter Sorotokin <psorotok@adobe.com>
CC: www-svg@w3.org

Peter Sorotokin wrote:
>> I want to dynamically execute the script at http://foo at runtime.  
>> Using language-dependent mechanisms in ECMAScript I have to somehow 
>> load the data into a string (dealing with character encodings in the 
>> process) and then call eval() on it?
> 
> Yes. Use URIRequest and eval.

And if I want to execute ECMAScript from Java or vice versa or either of 
those from some other language that has easy access to the DOM but can't 
easily evaluate the script string?  It looked to me like SVG was trying 
to really support Java and ECMAScript on an equal footing; was I wrong?

(Not to mention issues like trying to execute a JavaScript 1.2 script 
from inside JavaScript 1.3 and so forth... eval really does not cut it 
there).

>>   Using a <script> node, I just set the src attribute and insert the 
>> node.
> 
> I think this usage is a hack.

Very well.  Provide an alternate solution to the use cases this solves, 
then?  URIRequest and eval really don't cut it there.

> URIRequest and eval works just as well for that.

It does not, for the reason described above.

> Yes, I saw it; this implies that script element has some sort of a 
> hidden state that has to be managed it some way. I'd rather not 
> introduce it.

Again, feel free to propose other solutions to these common use cases...

-Boris
Received on Wednesday, 1 December 2004 20:40:01 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:29 GMT