XUL: Difference between revisions

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
imported>Arjayay
m Based off > Based on
 
imported>InternetArchiveBot
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5
 
Line 31: Line 31:
'''XUL''' ({{IPAc-en|ˈ|z|uː|l}} {{respell|ZOOL|'}}), which stands for '''XML User Interface Language''', is a [[user interface markup language]] developed by [[Mozilla]]. XUL is an [[XML]] dialect for writing [[graphical user interface]]s, enabling developers to write user interface elements in a manner similar to [[web page]]s.
'''XUL''' ({{IPAc-en|ˈ|z|uː|l}} {{respell|ZOOL|'}}), which stands for '''XML User Interface Language''', is a [[user interface markup language]] developed by [[Mozilla]]. XUL is an [[XML]] dialect for writing [[graphical user interface]]s, enabling developers to write user interface elements in a manner similar to [[web page]]s.


XUL [[application software|applications]] rely on the Mozilla [[codebase]] or a [[Fork (software development)|fork]] of it. The most prominent example is the [[Firefox]] web browser. However, Mozilla has significantly reduced the usage of XUL in Firefox after their rewrite of the browser engine in version 57.<ref name="life after xul"/><ref name = "problems with xul">{{Cite web|url=https://mozilla.github.io/firefox-browser-architecture/text/0003-problems-with-xul.html|title=Problems with XUL|website=mozilla.github.io|access-date=2019-06-07}}</ref> This resulted in the removal of the legacy [[Add-on (Mozilla)|add-on]] system, which relied on XUL and [[XPCOM]], another cross-platform technology Mozilla decided to deprecate shortly before the release of Firefox 57. Firefox originally permitted add-ons to extensively alter its user interface, but this capability was removed in 2017 and replaced with the less-permissive [[Browser extension#API conformity|WebExtensions API]].<ref name="57rel">{{Cite web|url=https://www.mozilla.org/en-US/firefox/57.0/releasenotes/|title=Firefox 57.0, See All New Features, Updates and Fixes|website=Mozilla |date=14 November 2017 |access-date=27 September 2022}}</ref><ref name="2015blog">{{cite web|title=The Future of Developing Firefox Add-ons|url=https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/|date=2015-08-21|author=Kev Needham|access-date=2018-04-02|website=blog.mozilla.org}}</ref> Several [[Fork (software development)|fork]]s of Firefox retain support for XUL and XPCOM-based add-ons. [[Waterfox]] maintains a fork of the legacy Mozilla codebase for the ''Waterfox Classic'' browser.<ref>{{cite web|title=Waterfox, Its Legacy and Looking to the Future|url=https://blog.waterfoxproject.org/waterfox-its-legacy-and-looking-to-the-future|website=Waterfox blog|date=2018-04-28|access-date=2018-06-20|last=Kontos |first=Alex}}</ref> The [[Pale Moon]] browser,<ref>{{cite web|url=https://www.palemoon.org/roadmap.shtml |title=Pale Moon future roadmap | access-date=2018-04-02 |publisher=Moonchild Productions |date=23 March 2022 |website=palemoon.org}}</ref> [[Basilisk (web browser)|Basilisk]] browser,<ref>{{cite news|title=Pale Moon team releases first version of Basilisk browser|url=https://www.ghacks.net/2017/11/17/pale-moon-team-releases-first-version-of-basilisk-browser/|newspaper=Ghacks Technology News|date=2017-11-17 |last=Brinkmann |first=Martin |access-date=2018-04-02}}</ref> [[Hyperbola GNU/Linux-libre|Hyperbola]] operating system,<ref>[https://wiki.hyperbola.info/doku.php?id=en:project:iceweasel-uxp Iceweasel-UXP project page] {{webarchive|url=https://web.archive.org/web/20211229042029/https://wiki.hyperbola.info/doku.php?id=en:project:iceweasel-uxp|date=December 29, 2021}}</ref> and numerous smaller projects collectively use and maintain the Unified XUL Platform (UXP) implementation.  
XUL [[application software|applications]] rely on the Mozilla [[codebase]] or a [[Fork (software development)|fork]] of it. The most prominent example is the [[Firefox]] web browser. However, Mozilla has significantly reduced the usage of XUL in Firefox after their rewrite of the browser engine in version 57.<ref name="life after xul"/><ref name = "problems with xul">{{Cite web|url=https://mozilla.github.io/firefox-browser-architecture/text/0003-problems-with-xul.html|title=Problems with XUL|website=mozilla.github.io|access-date=2019-06-07}}</ref> This resulted in the removal of the legacy [[Add-on (Mozilla)|add-on]] system, which relied on XUL and [[XPCOM]], another cross-platform technology Mozilla decided to deprecate shortly before the release of Firefox 57. Firefox originally permitted add-ons to extensively alter its user interface, but this capability was removed in 2017 and replaced with the less-permissive [[Browser extension#API conformity|WebExtensions API]].<ref name="57rel">{{Cite web|url=https://www.mozilla.org/en-US/firefox/57.0/releasenotes/|title=Firefox 57.0, See All New Features, Updates and Fixes|website=Mozilla |date=14 November 2017 |access-date=27 September 2022}}</ref><ref name="2015blog">{{cite web|title=The Future of Developing Firefox Add-ons|url=https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/|date=2015-08-21|author=Kev Needham|access-date=2018-04-02|website=blog.mozilla.org}}</ref> Several [[Fork (software development)|fork]]s of Firefox retain support for XUL and XPCOM-based add-ons. [[Waterfox]] maintains a fork of the legacy Mozilla codebase for the ''Waterfox Classic'' browser.<ref>{{cite web|title=Waterfox, Its Legacy and Looking to the Future|url=https://blog.waterfoxproject.org/waterfox-its-legacy-and-looking-to-the-future|website=Waterfox blog|date=2018-04-28|access-date=2018-06-20|last=Kontos|first=Alex|archive-date=April 12, 2019|archive-url=https://web.archive.org/web/20190412134139/https://blog.waterfoxproject.org/waterfox-its-legacy-and-looking-to-the-future|url-status=dead}}</ref> The [[Pale Moon]] browser,<ref>{{cite web|url=https://www.palemoon.org/roadmap.shtml |title=Pale Moon future roadmap | access-date=2018-04-02 |publisher=Moonchild Productions |date=23 March 2022 |website=palemoon.org}}</ref> [[Basilisk (web browser)|Basilisk]] browser,<ref>{{cite news|title=Pale Moon team releases first version of Basilisk browser|url=https://www.ghacks.net/2017/11/17/pale-moon-team-releases-first-version-of-basilisk-browser/|newspaper=Ghacks Technology News|date=2017-11-17 |last=Brinkmann |first=Martin |access-date=2018-04-02}}</ref> and numerous smaller projects collectively use and maintain the Unified XUL Platform (UXP) implementation.  


== History ==
== History ==
Line 47: Line 47:


When Mozilla removed support from Firefox, there were still several applications using XUL. Mozilla began gradually removing XUL support from their email client, [[Mozilla Thunderbird|Thunderbird]]. They released Thunderbird 78 without support for XUL-based extensions in 2020.<ref>{{cite web|url=https://developer.thunderbird.net/add-ons/updating/tb78/changes |title=Adapt to Changes in Thunderbird 69-78 |website=developer.thunderbird.net |access-date=27 September 2022 |date=2022}}</ref>
When Mozilla removed support from Firefox, there were still several applications using XUL. Mozilla began gradually removing XUL support from their email client, [[Mozilla Thunderbird|Thunderbird]]. They released Thunderbird 78 without support for XUL-based extensions in 2020.<ref>{{cite web|url=https://developer.thunderbird.net/add-ons/updating/tb78/changes |title=Adapt to Changes in Thunderbird 69-78 |website=developer.thunderbird.net |access-date=27 September 2022 |date=2022}}</ref>
The [[SeaMonkey]] internet suite chose to re-implement XUL for the Firefox Quantum codebase, and the suite's development has subsequently slowed. The [[Pale Moon]] developers forked Mozilla's entire Firefox 52 ESR codebase to create the Unified XUL Platform [[Pale Moon#Unified XUL Platform (UXP)|(UXP)]] for their [[Goanna (software)|Goanna]] rendering engine. UXP maintains the traditional XUL capabilities.<ref>{{cite web|url=https://forum.palemoon.org/viewtopic.php?f=62&t=17213|title=UXP vs goanna |last=Straver |first=Markus |access-date=27 September 2022 |date=2 November 2017 |quote=The plan is to switch Pale Moon over from our current platform to UXP (long-term plans) because a developed and maintained XUL-based platform is the only way a XUL application (like Pale Moon) has any chance of surviving without falling into obsolescence, with Mozilla abandoning this technology. That has been the main reason why I decided to start on this platform to begin with! Regardless, the platform will not be solely developed for Pale Moon's potential future use, it is developed for any future XUL application that will otherwise be dead in the water. Basically we're taking over the torch from Mozilla in developing and maintaining a platform for XUL applications of any kind; Mozilla should not be seen as "upstream" because it isn't.}}</ref> As a result, Pale Moon and other UXP applications have remained single-process but more extensible compared to modern versions of Firefox and Thunderbird.<ref>{{cite web |title=There is only XUL |url=http://thereisonlyxul.org/ |archive-url=https://web.archive.org/web/20180917071644/http://thereisonlyxul.org/ |archive-date=17 September 2018 |last=Tobin |first=Matt |access-date=18 September 2018}}</ref>
The [[SeaMonkey]] internet suite chose to re-implement XUL for the Firefox Quantum codebase, and the suite's development has subsequently slowed. The [[Pale Moon]] developers forked Mozilla's entire Firefox 52 ESR codebase to create the Unified XUL Platform [[Pale Moon#Unified XUL Platform (UXP)|(UXP)]] for their [[Goanna (software)|Goanna]] rendering engine. UXP maintains the traditional XUL capabilities.<ref>{{cite web |url=https://forum.palemoon.org/viewtopic.php?f=62&t=17213 |title=UXP vs goanna |last=Straver |first=Markus |access-date=27 September 2022 |date=2 November 2017 |quote=The plan is to switch Pale Moon over from our current platform to UXP (long-term plans) because a developed and maintained XUL-based platform is the only way a XUL application (like Pale Moon) has any chance of surviving without falling into obsolescence, with Mozilla abandoning this technology. That has been the main reason why I decided to start on this platform to begin with! Regardless, the platform will not be solely developed for Pale Moon's potential future use, it is developed for any future XUL application that will otherwise be dead in the water. Basically we're taking over the torch from Mozilla in developing and maintaining a platform for XUL applications of any kind; Mozilla should not be seen as "upstream" because it isn't. |archive-date=November 11, 2020 |archive-url=https://web.archive.org/web/20201111192226/https://forum.palemoon.org/viewtopic.php?f=62&t=17213 |url-status=dead }}</ref> As a result, Pale Moon and other UXP applications are more extensible compared to modern versions of Firefox and Thunderbird.<ref>{{cite web |title=There is only XUL |url=http://thereisonlyxul.org/ |archive-url=https://web.archive.org/web/20180917071644/http://thereisonlyxul.org/ |archive-date=17 September 2018 |last=Tobin |first=Matt |access-date=18 September 2018}}</ref>


== Usage ==
== Usage ==

Latest revision as of 02:47, 21 July 2025

Template:Short description Script error: No such module "Infobox".Template:Template otherScript error: No such module "Check for unknown parameters". Template:Use mdy dates

XUL (Template:IPAc-en Template:Respell), which stands for XML User Interface Language, is a user interface markup language developed by Mozilla. XUL is an XML dialect for writing graphical user interfaces, enabling developers to write user interface elements in a manner similar to web pages.

XUL applications rely on the Mozilla codebase or a fork of it. The most prominent example is the Firefox web browser. However, Mozilla has significantly reduced the usage of XUL in Firefox after their rewrite of the browser engine in version 57.[1][2] This resulted in the removal of the legacy add-on system, which relied on XUL and XPCOM, another cross-platform technology Mozilla decided to deprecate shortly before the release of Firefox 57. Firefox originally permitted add-ons to extensively alter its user interface, but this capability was removed in 2017 and replaced with the less-permissive WebExtensions API.[3][4] Several forks of Firefox retain support for XUL and XPCOM-based add-ons. Waterfox maintains a fork of the legacy Mozilla codebase for the Waterfox Classic browser.[5] The Pale Moon browser,[6] Basilisk browser,[7] and numerous smaller projects collectively use and maintain the Unified XUL Platform (UXP) implementation.

History

File:PeriodicTableofXUL Windows10 PaleMoon31.png
The Periodic Table of XUL Elements is a reference extension designed to demonstrate XUL's capabilities.

XUL was devised at Netscape in 1997 as part of the development effort that eventually became the Mozilla codebase.[8] XUL is similar to web technologies implemented by the Gecko rendering engine. When XUL was introduced, it added features beyond the then standard HTML 4. It was designed as an extension of HTML to be used with applications rather than documents.[9]

XUL was used by various Mozilla projects, forks of Mozilla projects, and projects closely related to Mozilla. Some software projects such as Songbird, Komodo IDE, and Zotero started as desktop applications that utilized XULRunner to render and compose their UI. In the early 2000s, there was some interest in using XUL by other parties, including Amazon,[10] but those have switched over to HTML5.[1][2] Many of the features of modern web technologies such as HTML5, CSS3, ECMAScript 5+, WebGL, and WebAssembly that made rich and modern web applications possible, without the need of utilizing legacy NPAPI/PPAPI/ActiveX browser plug-in technologies like Adobe Flash, Silverlight, Java, or Shockwave, also made much of XUL redundant.[9]

Mozilla released Firefox 57, also known as Firefox Quantum, in November 2017. As part of this, Firefox finished transitioning to a multiprocess architecture. Although XUL add-ons could work in this architecture, they often created significant performance issues. Because of this, Mozilla removed support for legacy add-ons, including the use of custom XUL code.[3][4] Mozilla switched their browser extensions system to the cross-browser WebExtensions API, which is largely based on the Chrome extension API. In late 2017, Firefox still included 289 XUL bindings for native browser components. By the end of 2019, Mozilla had removed all XUL files from their mozilla-central repository.[11][1][2]

When Mozilla removed support from Firefox, there were still several applications using XUL. Mozilla began gradually removing XUL support from their email client, Thunderbird. They released Thunderbird 78 without support for XUL-based extensions in 2020.[12] The SeaMonkey internet suite chose to re-implement XUL for the Firefox Quantum codebase, and the suite's development has subsequently slowed. The Pale Moon developers forked Mozilla's entire Firefox 52 ESR codebase to create the Unified XUL Platform (UXP) for their Goanna rendering engine. UXP maintains the traditional XUL capabilities.[13] As a result, Pale Moon and other UXP applications are more extensible compared to modern versions of Firefox and Thunderbird.[14]

Usage

XUL can only be used with the Mozilla codebase (or a fork of it) because the Gecko (or Goanna) engine does the XUL rendering.[15]

Application programmers need to define a XUL interface as three discrete sets of components:

  1. Content: the XUL document(s), whose elements define the layout of the user interface
  2. Skin: the CSS and image files, which define the appearance of an application
  3. Locale: the files containing user-visible strings for easy software localization

XUL defines a wide range of elements, which roughly belong to the following types:

The default behavior of XUL widgets can be altered with XBL bindings.

XBL

Script error: No such module "Labelled list hatnote". XML Binding Language (XBL) is an XML-based markup language for altering the behavior of a XUL widget, such as a scroll bar.[16][17] An XBL file contains bindings, each of which describes the behavior of a XUL widget. The root element of an XBL file is the <bindings> element, which contains one or more <binding> elements. Each <binding> element declares one binding, which can be attached to any XUL element. It may also possess an id attribute. A binding is assigned to an element by setting the CSS property -moz-binding to the URL of the binding's file.[18] For example:

scrollbar {
  -moz-binding: url('somefile.xml#binding1');
}

Example

This example shows three buttons stacked on top of each other in a vertical box container:[19]

File:Boxes-ex1.png
<?xml version="1.0"?>
<?xml-stylesheet href="chrome://global/skin/" type="text/css"?>

<window id="vbox example" title="Example 3...."
xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">
  <layout>
    <button id="yes1" label="Yes"/>
    <button id="no1" label="No"/>
    <button id="maybe1" label="Maybe"/>
  </layout>
</window>

Ghostbusters reference

XUL contains a reference to the 1984 film Ghostbusters.[20] The film's antagonist is the fictional deity Zuul, the Gatekeeper.[21] Zuul possesses the character Dana Barrett and declares: "There is no Dana. There is only Zuul."[22][20] The creators of XUL, pronounced the same as Zuul,[23] made the slogan, "There is no data. There is only XUL!".[24] The slogan and Zuul as a gatekeeper are referenced in XUL's XML namespace URI and were previously present in all Firefox add-ons:[20]

<templatestyles src="Template:Blockquote/styles.css" />

http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul

Script error: No such module "Check for unknown parameters".

See also

References

Template:Reflist

Template:Mozilla projects Template:Widget toolkits

Template:Authority control

  1. a b c Script error: No such module "citation/CS1".
  2. a b c Script error: No such module "citation/CS1".
  3. a b Script error: No such module "citation/CS1".
  4. a b Script error: No such module "citation/CS1".
  5. Script error: No such module "citation/CS1".
  6. Script error: No such module "citation/CS1".
  7. Script error: No such module "citation/CS1".
  8. Script error: No such module "citation/CS1".
  9. a b Script error: No such module "citation/CS1".
  10. Script error: No such module "citation/CS1".
  11. Script error: No such module "citation/CS1".
  12. Script error: No such module "citation/CS1".
  13. Script error: No such module "citation/CS1".
  14. Script error: No such module "citation/CS1".
  15. Script error: No such module "citation/CS1".
  16. Script error: No such module "citation/CS1".
  17. Script error: No such module "citation/CS1".
  18. Script error: No such module "citation/CS1".
  19. Script error: No such module "citation/CS1".
  20. a b c d Script error: No such module "citation/CS1".
  21. Script error: No such module "citation/CS1".
  22. Script error: No such module "citation/CS1".
  23. Script error: No such module "citation/CS1".
  24. Script error: No such module "citation/CS1".