[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: KHTML, KJS Unfrozen -- details
From:       Richard Moore <richmoore44 () gmail ! com>
Date:       2006-01-11 0:01:01
Message-ID: 5491a5150601101601i21ea7d10n336b2ef7ea6078d8 () mail ! gmail ! com
[Download RAW message or body]

On 1/10/06, Charles Samuels <charles@kde.org> wrote:
>
> I think it'd be nice if Javascripts executed incrementally (like on a
> QTimer(0) ).


I don't really see how that could be acheived unfortunately. It would
require an interpreter that made no use of the stack (which would be nice
for other reasons), but would also have a massive performance overhead that
would render sites that use js heavily unusable. Integrating a design like
this into applications that use JS outside web pages would be tricky too.

Rich.

[Attachment #3 (text/html)]

<br><br>
<div><span class="gmail_quote">On 1/10/06, <b class="gmail_sendername">Charles \
Samuels</b> &lt;<a href="mailto:charles@kde.org">charles@kde.org</a>&gt; \
wrote:</span> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px \
0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I think it'd be nice if Javascripts \
executed incrementally (like on a<br>QTimer(0) ).</blockquote> <div>&nbsp;</div>
<div>I don't really see how that could be acheived unfortunately. It would require an \
interpreter that made no use of the stack (which would be nice for other reasons), \
but would also have&nbsp;a massive performance overhead that would render sites that \
use js heavily unusable. Integrating a design like this into applications that use JS \
outside web pages would be tricky too. </div>
<div>&nbsp;</div>
<div>Rich.</div>
<div>&nbsp;</div><br>&nbsp;</div><br>



[prev in list] [next in list] [prev in thread] [next in thread]