Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


#301 javascript engine


Apparently, KompoZer has no javascript engine. And, while KompoZer is still in development, it is inappropriate to make the claim "Its remarkable support of XML, CSS and JavaScript offers the best authoring platform on the market.", where the "remarkable support" for JavaScript is simply to remark upon a nonexistent javascript engine. Without the javascript engine, KompoZer should not be called a WYSIWYG editor.

Of most concern, though, is that I can find no mention of the missing javascript engine, and no mention of any road-map to including a javascript engine on the KompoZer website. So, the question arises, "Will there be any plan to include a javascript engine in KompoZer?"


  • James


    From the website:

    SpiderMonkey is Mozilla's JavaScript engine written in C/C++. It is used in various Mozilla products, including Firefox, and is available under MPL/GPL/LGPL tri-license.

    The most recent standalone source code release implements JavaScript 1.8.5, and is largely the same engine that shipped with Firefox 4. To find out more about this version of SpiderMonkey, check out the Release Notes. You can download full source code here: http://ftp.mozilla.org/pub/mozilla.org/js/js185-1.0.0.tar.gz

    There are other options to SpiderMonkey, but they should not be necessary:


    About TraceMonkey

    TraceMonkey adds native‐code compilation to Mozilla’s JavaScript® engine (known as “SpiderMonkey”). It is based on a technique developed at UC Irvine called “trace trees”, and building on code and ideas shared with the Tamarin Tracing project. The net result is a massive speed increase both in the browser chrome and Web‐page content.

    And this:


    JaegerMonkey (or JägerMonkey) is a new method JIT for SpiderMonkey. The goal is to get reliable baseline performance on the order of other JS JIT systems. JM will be a baseline whole-method JIT that doesn't necessarily do many traditional compiler optimizations. Instead, it does dynamic-language-JIT-oriented optimizations like PICs and specialization of constant operands.