Extension:Popups/ru

Расширение Popups отображает предварительный просмотр страниц и ссылок при наведении курсора на ссылку на статью или, соответственно, на ссылку. Первый состоит из резюме содержания статьи, второй показывает полное содержание ссылки.

Это инициатива команды дизайнеров, вдохновленных популярным гаджетом Навигационные окошки. В настоящее время эта функция доступна во всех Википедиях по умолчанию для вышедших из системы пользователей. Описание функций расширения и дополнительную информацию о его использовании в проектах Викимедиа доступно в Page Previews.

The Reference Previews feature was added eventually and aims to fulfill a wish from the German-speaking community's Technical Wishlist. A more detailed description and more information on its use is available at.

Зависимости
Это расширение имеет жесткую зависимость от и  при использовании по умолчанию со шлюзом. Существуют также дополнительные зависимости от (без BetaFeatures, он загружается для всех пользователей),  и  (для инструментария).

Установка

 * Установите зависимости.

Page previews content
Всплывающие окна предварительного просмотра страницы показывают изображение (если оно доступно) и небольшой фрагмент текста.

Изображение
Изображение формируются при помощи, которое возвращает одну наиболее подходящую миниатюру, связанную со статьей. Он игнорирует шаблоны обслуживания, незавершённые статьи и т.д.

Текст
The page previews can be configured with any compatible API that is compatible with the Page content service summary endpoint using. For third parties we encourage using the Page Content Service to enjoy using Popups with your local wiki.

You can also use the extension. This extension has various caveats and we do not actively support use of this API.

Reference previews content


The content in the reference preview popups is taken directly from the reference section on the page itself. No external services are involved here. If the content exceeds the popup size scrollbars are shown so everything can be looked at.

Типы примечаний
The reference types displayed are set by using specific CSS-classes on the tag that can be used to encapsulate the content of a reference, e.g.. Currently the following types are supported:,  ,  ,  ,. Apart from that there is always a generic fallback if neither the cite tag was found nor an appropriate class was used. Please note, that it's not recommended to use the CSS-classes directly in wikitext, but rather by creating templates.

Renderers
This extensions currently has only one renderer, that is for ordinary pages.

New renderers for different kind of pages, or things like references can be easily added.

One needs to create a new object with the following methods:



You can see details of these methods in ext.popups.renderer.article.js or this patch that adds a renderer for references.



API предварительного просмотра страниц
Каждый проект уникален, и то, что отображается в превью, сильно зависит от содержимого вашей вики.

Расширение Popups оптимизировано для работы с контентом, подобным Википедии (например, викитекстом).

Если ваша вики использует другой тип обработчика содержимого (например, как в случае с ) потребуется предоставить собственный API.

API может быть написан на любом языке, но ответ API должен соответствовать спецификации указанной здесь:

Определение новых API выходит за рамки расширения Popups.

После определения вы можете настроить предварительный просмотр страниц, чтобы они указывали на ваш API, используя параметр конфигурации.



Известные проблемы

 * Users of the extension should note that Page Previews requests previews in the content language of the page. If the preview contains a complete translatable block, then it will be translated. If, however, the preview contains an incomplete translateable block – because a sentence is cut off, say – then it isn't translated and will be displayed in the content language of the page. If you are observing this behavior, then you should consider marking up individual sentences in your lead section. T167852 is for a technical audience but has more information on the underlying problem.
 * Longer math formulas cutting off in preview - long math or chemical formulas (formulas wider than the preview width) display as truncated in previews. We were not able to add a gradient in order to indicate that the formula is continued on the article itself.
 * Small files may be in the "Рage information" (action=info), but not in the "Popups". Some requirements are set here - for a portrait image: exact (min) height 250 px & max width 203 px; for a landscape image: exact (min) width 320 px &  max height 200 px . To display, images must be able to become a thumbnail that is larger or equal to these "exact" sizes. (If you are cropping a large image to make a leading picture for an article, be sure that the picture you are creating is not smaller than the specified sizes.)

Extensibility
In MediaWiki 1.40, extensions and skins can extend the page previews functionality with their own custom preview types. It does this by registering a PluginModules attribute in its extension.json or skin.json file that points to a ResourceLoaderModule that can register a preview type. The plugin module should export information about when the preview should be displayed (via selector), and how the preview data should be retrieved (via gateway library). This feature is still in its infancy, has a few bugs (example) and feedback/bug reports via Phabricator are encouraged.

Why can't I copy and paste text from a preview?
At time of writing, the cons of doing so outweigh the pros. Essentially it boils down to decreasing the touch area to read the article in full. Once Page Previews is deployed on English and German Wikipedia, feel free to reopen this task and reignite the discussion, but right now we have no plans.

How can I change the image that I see on preview?
See Extension:PageImages#Image choice.

How can I remove content from a page preview?
Any element marked with the  class will be stripped from the summary.

Why is content removed from the summary?
Any HTML element marked with the class,  ,  ,  ,  ,   or   will be removed from the summary. If the text should be displayed in the summary, you should under no circumstances use these classes in any templates that are used within the beginning section of an article.

Where do summaries come from?
These are provided by the summary REST API (Wikimedia production wikis) or the API in case your wiki is using the default   gateway.

Why are parenthetical stripped?
There's a good discussion going on in T91344 in Phabricator. If you have any views on this or see any problems relating to this, please let us know there.

Why don't I see Popups outside of content namespaces?
Popups appear on links to pages in content namespaces only. This is a limitation of Popups; TextExtracts are available from other namespaces. You may work around this by appending more namespaces into.

Ссылки

 * Page Previews help page and central feedback page on MediaWiki.org
 * Reference Previews help page and central feedback page on MediaWiki.org
 * Reference Previews main project page on Meta
 * Related research: Wikimedia Performance Team/Authoring Popups: Best Practices