|
CommonJS
CommonJS is a project with the goal to establish conventions on the module ecosystem for JavaScript outside of the web browser. The primary reason for its creation was a major lack of commonly accepted forms of JavaScript module units which could be reusable in environments different from that provided by conventional web browsers running JavaScript scripts (e.g. web servers or native desktop applications). CommonJS's module specification is widely used today, in particular for server-side JavaScript programming with Node.js. It is also used in the development of browser-side JavaScript, but the code must be packaged with a transpiler since browsers don't support CommonJS. The other major module specification in use is the ECMAScript (ES) modules specification (ES6 modules aka ES2015 modules). CommonJS can be recognized by the use of the require() function and module.exports, while ES modules use import and export statements for similar (though not identical) functionality. Hi ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
XULJet
XULJet was an open-source JavaScript framework for the Mozilla XULRunner run-time environment. It is intended for writing desktop applications in pure JavaScript. XULJet provides a component architecture and user interface elements description inspired by Seaside. It implements some CommonJS specifications. Examples Hello world in XULJet: var xuljet = require("lib/xuljet") var Main = function(aWindow) xuljet.inherits(Main, xuljet.Component) Main.prototype.render = function(xul) function main() See also * JavaScript JavaScript (), often abbreviated as JS, is a programming language that is one of the core technologies of the World Wide Web, alongside HTML and CSS. As of 2022, 98% of Website, websites use JavaScript on the Client (computing), client side ... * XUL * XULRunner * CommonJS References External links *{{Official website, https://code.google.com/p/xuljet/Javascript Libraries [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Comparison Of Server-side JavaScript Solutions
This is a list of server-side JavaScript implementations. Server-side JavaScript use Other common server-side programming languages are JavaServer Pages (JSP), Active Server Pages (ASP), Perl, PHP, Python (programming language), Python, Ruby programming language, Ruby, ColdFusion, and others. See also * References External linksThe Server-Side JavaScript Google Groupdedicated to creating cross-platform SSJS standard APIs.Mozilla JavaScript shells especially section "Standalone JavaScript shells" {{ECMAScript JavaScript Software comparisons, Server-side JavaScript implementations Lists of software, Server-side JavaScript implementations ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
JSGI
JSGI, or JavaScript Gateway Interface, is an interface (computer science), interface between web servers and JavaScript-based web applications and web framework, frameworks. It was inspired by the Rack (web server interface), Rack for Ruby (programming language), Ruby and Web Server Gateway Interface, WSGI for Python (programming language), Python and was one of the inspirations of PSGI for Perl. is a reference implementation of JSGI. It has been included in and further developed by the CommonJS project. JSGI packages All these packages are for Nodejs, Node.JS. Low level Q-IO Promise-based I/O, includes JSGI based HTTP server and client jsgi-node Low level JSGI interface for Node.JS Framework These frameworks allow using Promise (programming), promises with Q: * * The names are inspired by Sinatra (software), Sinatra. References External links JSGI 0.3 specification * * JavaScript libraries {{compu-prog-stub ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Asynchronous Module Definition
Asynchronous module definition (AMD) is a specification for the programming language JavaScript. It defines an application programming interface (API) that defines code modules and their dependencies, and loads them asynchronously if desired. Implementations of AMD provide the following benefits: * Website performance improvements. AMD implementations load smaller JavaScript files, and then only when they are needed. * Fewer page errors. AMD implementations allow developers to define dependencies that must load before a module is executed, so the module does not try to use outside code that is not available yet. In addition to loading multiple JavaScript files at runtime, AMD implementations allow developers to encapsulate code in smaller, more logically-organized files, in a way similar to other programming languages such as Java. For production and deployment, developers can concatenate and minify JavaScript modules based on an AMD API into one file, the same as traditional Ja ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
QUnit
QUnit is a JavaScript unit testing framework. Originally developed for testing jQuery, jQuery UI and jQuery Mobile, it is a generic framework for testing any JavaScript code. It supports client-side environments in web browsers, and server-side (e.g. Node.js). QUnit's assertion methods follow the CommonJS unit testing specification, which itself was influenced to some degree by QUnit. History John Resig originally developed QUnit as part of jQuery. In 2008 it was extracted from the jQuery unit test code to form its project and became known as "QUnit". This allowed others to start using it for writing their unit tests. While the initial version of QUnit used jQuery for interaction with the DOM, a rewrite in 2009 made QUnit completely standalone. Usage and examples * QUnit.module(string) - Defines a module, a grouping of one or more tests. * QUnit.test(string, function) - Defines a test. QUnit uses a set of assertion method to provide semantic meaning in unit tests: * ass ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Jetpack (Firefox Project)
Jetpack was a working group which wrote a software development kit for Firefox add-ons. They produced the Add-on SDK, a set of APIs, a runtime, and a command-line tool for creating and running add-ons, and the Add-on Builder, a Web-based integrated development environment which used the SDK. Add-ons developed with the SDK were written in HTML, CSS, and JavaScript using CommonJS CommonJS is a project with the goal to establish conventions on the module ecosystem for JavaScript outside of the web browser. The primary reason for its creation was a major lack of commonly accepted forms of JavaScript module units which could ... conventions. They did not require the user to restart Firefox when they were installed or uninstalled. The SDK's APIs were high-level, task-oriented, and designed to insulate developers from changes across Firefox versions. Mozillians running the project made a tool called the Jetpack Prototype. APIs provided by the Jetpack Prototype were not compatibl ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
SproutCore
SproutCore is an open-source JavaScript web framework. Its goal is to allow developers to create web applications with advanced capabilities and a user experience comparable to that of desktop applications. When developing a SproutCore application, all code is written in JavaScript. A notable fork of SproutCore is Ember.js. Both projects are maintained separately and have taken different directions. Development SproutCore, initially created in 2007 by Sproutit as the basis for their Mailroom application, is available under the MIT License. Apple announced MobileMe at WWDC in 2008, noting that much of it was built using SproutCore. Apple has contributed greatly to the project as part of a Web 2.0 initiative. SproutCore was also used at iWork.com, the online extension of the iWork productivity software by Apple. The latest major stable SproutCore release is 1.8, released on March 7, 2012, with many bug fixes, several new features, and documentation updates. Release 1.6 was ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Application Programming Interface
An application programming interface (API) is a way for two or more computer programs to communicate with each other. It is a type of software interface, offering a service to other pieces of software. A document or standard that describes how to build or use such a connection or interface is called an ''API specification''. A computer system that meets this standard is said to ''implement'' or ''expose'' an API. The term API may refer either to the specification or to the implementation. In contrast to a user interface, which connects a computer to a person, an application programming interface connects computers or pieces of software to each other. It is not intended to be used directly by a person (the end user) other than a computer programmer who is incorporating it into the software. An API is often made up of different parts which act as tools or services that are available to the programmer. A program or a programmer that uses one of these parts is said to ''call'' that ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Client-side
Client-side refers to operations that are performed by the client in a client–server relationship in a computer network. General concepts Typically, a client is a computer application, such as a web browser, that runs on a user's local computer, smartphone, or other device, and connects to a server as necessary. Operations may be performed client-side because they require access to information or functionality that is available on the client but not on the server, because the user needs to observe the operations or provide input, or because the server lacks the processing power to perform the operations in a timely manner for all of the clients it serves. Additionally, if operations can be performed by the client, without sending data over the network, they may take less time, use less bandwidth, and incur a lesser security risk. When the server serves data in a commonly used manner, for example according to standard protocols such as HTTP or FTP, users may have their choice ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Document Object Model
The Document Object Model (DOM) is a cross-platform and language-independent interface that treats an XML or HTML document as a tree structure wherein each node is an object representing a part of the document. The DOM represents a document with a logical tree. Each branch of the tree ends in a node, and each node contains objects. DOM methods allow programmatic access to the tree; with them one can change the structure, style or content of a document. Nodes can have event handlers attached to them. Once an event is triggered, the event handlers get executed. The principal standardization of the DOM was handled by the World Wide Web Consortium (W3C), which last developed a recommendation in 2004. WHATWG took over the development of the standard, publishing it as a living document. The W3C now publishes stable snapshots of the WHATWG standard. In HTML DOM (Document Object Model), every element is a node: * A document is a document node. * All HTML elements are element nodes. * ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
