In 2020 it was adopted for use in MediaWiki, and it has already seen use within some MediaWiki extensions, such as NearbyPages. Vue.js, also known as just Vue, was first released in 2014, and is often listed alongside frameworks like Angular and React though Vue.js is usually considered simpler to use than those other two. – one of the batch of “modern JavaScript frameworks” that are currently taking over the world of JavaScript programming (and web programming in general). Nevertheless, these two libraries have not only been ignored outside of MediaWiki, but are now on their way out within MediaWiki as well. It is actually somewhat unfortunate that they never got more widespread use, because OOUI's user interface elements are overall quite well done – in terms of their internationalization (translation into many languages, right-to-left display display, etc.) and accessibility (support for the visually impaired, etc.), but also just in their overall look-and-feel. They were first created in 2013 for use by the VisualEditor extension, but eventually came to be used throughout core MediaWiki, and in many of its extensions. They are sister libraries, in the same manner as jQuery and jQuery UI. They have generic-sounding names and can in theory be used in any application, but in practice they have only ever been used within MediaWiki. – a pair of JavaScript libraries whose names are short for “Object-Oriented JavaScript” and “Object-Oriented JavaScript User Interface”, respectively. jQuery UI was added to core MediaWiki in 2010, at the same time as jQuery, and it remains there, but its usage in MediaWiki and extensions has dropped to nearly zero. Even before then, though, MediaWiki developers had wanted to stop using it, because it lacks sufficient support for accessibility and internationalization. In 2017, development on it essentially stopped, with no official explanation given. – that are only possible with JavaScript. It defines a large set of user interface widgets – comboboxes, tabs, etc. – a sister library to jQuery, though it has had quite a different “career trajectory”. jQuery has been included in MediaWiki since 2010. It offers a logical way to access and modify the different elements of the HTML (or DOM, if you prefer calling it that). This is a slight decline from its peak of 97% around 2020, but jQuery still dominates. – by far the most popular JS library in the world, currently used by 95% of all websites with a known JS library, according to the site. Let's take a look at some of the JavaScript libraries that MediaWiki makes use of, to understand both the current state and where things are headed: If you go with this approach, you would still most likely want to block non-logged-in users from being able to edit the wiki, but that's easy to accomplish (see here). The custom actions are usually still there, if users manually type in URLs that end with "action=history" and the like but the absence of links on the screen will mean that the vast majority of users will never know that there's a wiki behind the scenes, let alone see the history of page, the set of recent changes, etc. The idea is that users who can edit the wiki (of whom there will be relatively few), and who are logged in, will see the wiki with a normal skin while the majority of users/readers, who aren't logged in, will see the wiki with a custom skin that doesn't show the history and edit tabs, the standard sidebar, etc.: it's a lightweight method of making a regular-looking website with the editing convenience of a wiki. One interesting, unconventional usage of skins is as a way to turn a wiki into a more standard content-publishing system.
0 Comments
Leave a Reply. |