Skip to main content

Home/ javascript/ Group items tagged mozilla

Rss Feed Group items tagged

Mike Chelen

Bespin » Code in the Cloud - 0 views

  •  
    Bespin is a Mozilla Labs experiment on how to build an extensible Web code editor using HTML 5 technology.
Javier Neira

Inheritance - MDC - 1 views

  • Note that __proto__ may not be available in JavaScript versions other than that in Mozilla. An alternative, but less optimal version of extend(), which should work everywhere, is: function extend(child, super) { for (var property in super.prototype) { if (typeof child.prototype[property] == "undefined") child.prototype[property] = super.prototype[property]; } return child; }
Julian Knight

Xinha - Trac - 0 views

  •  
    Xinha (pronounced like Xena, the Warrior Princess) is a powerful WYSIWYG HTML editor component that works in Mozilla based browsers as well as in MS Internet Explorer. Its configurabilty and extensibility make it easy to build just the right editor for multiple purposes, from a restricted mini-editor for one database field to a full-fledged website editor. Its liberal licence makes it an ideal candidate for integration into any kind of project.
Ivan Pavlov

XRAY :: for web developers - 0 views

shared by Ivan Pavlov on 04 Aug 08 - Cached
  • XRAY is a bookmarklet for Internet Explorer 6+, and Webkit and Mozilla based browsers (including Safari, Firefox, Camino or Mozilla). Use it to see the box model for any element on any web page.
anonymous

SlimerJS - 3 views

  •  
    SlimerJS is useful to do functional tests, page automation, network monitoring, screen capture, etc. SlimerJS is similar to PhantomJs, except that it runs on top of Gecko, the browser engine of Mozilla Firefox (specifically, version 31), instead of Webkit, and is not yet truly headless.
Ivan Pavlov

FUEL - MozillaWiki - 0 views

  •  
    Firefox User Extension Library) is a JavaScript Library designed to help developers build extensions using terminology and interfaces that are familiar to them.
Javier Neira

JavaScript EE, Part 1: Run JavaScript files on the server side - 0 views

  • freedom to use the same JavaScript routines on both servers and clients. In addition, the techniques presented throughout this series will allow you to maintain a single code base for both Ajax and non-Ajax clients
  • This double-coding issue can be avoided by using JavaScript combined with Java code on the server side, getting full support of scripting languages through the javax.script API. In addition, the Java SE Development Kit (JDK) 6 already includes Mozilla's Rhino JavaScript engine, which means no setup is required.
  • the toSource() method, which all JavaScript objects must have.
  • ...5 more annotations...
  • engine.eval(scriptReader, vars);
  • sun.org.mozilla.javascript.internal.NativeObject
  • all data exchange between the Java code and the executed script should be done through primitive variables, strings, and Java objects (for example, beans) whose properties and methods can be accessed very easily in the JavaScript code. Simply said, don't try to access native JavaScript objects in your Java code. Use Java objects in the JavaScript code instead.
  • Note that javax.script.Invocable is an optional interface, which some script engines may not implement. The JavaScript engine that comes with JDK 6 does support this interface.
  • you can significantly reduce the execution time by compiling the scripts, using the methods provided by another optional interface named javax.script.Compilable, which is supported by the JavaScript engine of JDK 6.
1 - 11 of 11
Showing 20 items per page