Manual:Developing extensions/zh



每个扩展都由三部分组成：


 * 1) 配置
 * 2) 执行
 * 3) 本地化

一个最小的扩展只需如下结构：


 * MyExtension/extension.json: 存储安装说明. 文件名必须为 extension.json. （在MediaWiki 1.25之前，安装说明位于以扩展名命名的 文件中.  许多扩展在此PHP文件中仍然具有向后兼容的填充. ）
 * MyExtension/includes/: 存储扩展的PHP可执行代码. ;
 * MyExtension/resources/: 存储扩展的客户端资源，例如JavaScript，CSS和LESS.
 * MyExtension/i18n/*.json: 存储扩展的本地化信息.

当您在开发扩展时，请将上文中的MyExtension替换为您开发的扩展的名字. 使用大驼峰式命名法来命名文件夹和PHP文件，这是文件命名的惯例. （对于开发您的扩展是一个好的开始. ）

配置
编写设置部分的最终目的是使扩展安装尽可能容易，因此用户只需将此行添加到LocalSettings.php中：

如果要使扩展用户可配置，则需要定义和记录一些配置参数，并且用户的设置应如下所示：

为了让这一操作变得简单，您的安装文件需要完成许多任务（以下各节中有详细描述）：


 * 注册您的扩展使用的所有媒体处理程序、解析器函数、特殊页面、自定义XML标签和变量.
 * 定义和/或验证为扩展定义的任何配置变量.
 * 准备您的扩展程序用于自动加载的类（class）
 * 确定哪些部分需要立即完成设置，哪些部分需要在MediaWiki核心已初始化和配置后再完成设置.
 * 定义您的扩展添加的额外的钩.
 * 创建或检查扩展所需的任何新数据库表.
 * 为您的扩展程序设置本地化.

通过MediaWiki注册功能
MediaWiki在其 页面上列出了已安装的所有扩展. 例如，您可以在Special:Version上查看此Wiki上安装的所有扩展.

为此，请将扩展详细信息添加到extension.json. 该部分将如下所示：

许多字段是可选的，但填写它们仍然是一个好习惯. 指的是文件所针对的架构版本. 可用的版本为1和2. 请参见有关此功能的文档. 除非需要支持较旧版本的MediaWiki，否则请选择最新版本.

除上述注册外，您还必须将功能“钩”到MediaWiki中. 上面仅设置了特殊:版本页面. 执行此操作的方式取决于您开发的扩展的类型. 有关详细信息，请参阅每种扩展类型的文档：

使您的扩展可由用户配置
如果您希望用户能够配置您的扩展程序，则需要提供一个或多个配置变量. 最好能给这些变量起一个唯一的名称. 同样需要遵循MediaWiki命名常规（例如，全局变量名应以$wg作为开始）.

例如，如果您扩展的名字为“MyExtension”，您可能需要将所有相关的配置变量以 作为开始. 重要的是，此时MediaWiki的内核变量尚未定义，您需要做一些合理的检查，以确保没有已发布的扩展以这种方式开始其变量命名. 用户不会因为您使用了重叠的变量名而在您的扩展和其它扩展之间选择.

同样建议在安装说明中包括所有配置变量的详尽文档.

以下是一个可以用来入门的示例样板：

注意：在 执行后，通用变量 不存在. 如果您给给变量赋值，则来自extension.json的值将不会被使用.

关于在扩展中使用通用变量，请参考.

将class准备用于自动加载
如果您决定使用类/对象开发您的扩展，媒体维基提供了一个简单的搜索类文件位置的方法. 在大多数情况下，这将免去开发自己的 方法.

如想使用媒体维基的自动加载功能，您需要向字段添加信息. 字段名称为类名称，内容为文件名. 对于一个简单的单类文件扩展，类文件经常与扩展同名. 所以您的自动加载部分内容可能是如下：

The filename is relative to the directory the extension.json file is in.

For more complex extensions, namespaces should be considered. See Manual:Extension.json/Schema#AutoloadNamespaces for details.

定义额外的钩子
参见.

Adding database tables
Make sure the extension doesn't modify the core database tables. Instead, extension should create new tables with foreign keys to the relevant MW tables.

If your extension needs to add its own database tables, use the hook. See the manual page for more information on usage.

Set up localisation
參見：
 * 本地化（摘要）
 * 本地化（详情）
 * Namespaces

添加日志
On MediaWiki, all actions by users on wiki are tracked for transparency and collaboration. See for how to do it.

Handling dependencies
Assume that an extension requires the presence of another extension, for example because functionalities or database tables are to be used and error messages are to be avoided in case of non-existence.

For example the extension requires the presence of the extension  for certain functions. Some ideas to figure this out:

This should work at least from 1.23 up to 1.35.

本地化
If you want your extension to be used on wikis that have a multi-lingual readership, you will need to add localisation support to your extension.

Store messages in .json
Store message definitions in a localisation JSON file, one for each language key your extension is translated in. The messages are saved with a message key and the message itself using standard JSON format. Each message id should be lowercase and may not contain spaces. Each key should begin with the lowercased extension name. An example you can find in the MobileFrontend extension. Here is an example of a minimal JSON file (in this case en.json:

en.json

Store message documentation in qqq.json
The documentation for message keys can be stored in the JSON file for the pseudo language with code qqq. A documentation of the example above can be:

qqq.json:

Load the localisation file
In your extension.json, define the location of your messages files (e.g. in directory i18n/):

Use wfMessage in PHP
In your setup and implementation code, replace each literal use of the message with a call to. In classes that implement (as well as some others such as subclasses of SpecialPage), you can use   instead. Example:

Use mw.message in JavaScript
It's possible to use i18n functions in JavaScript too. Look at for details.

扩展类型
Extensions can be categorized based on the programming techniques used to achieve their effect. Most complex extensions will use more than one of these techniques:


 *  Subclassing:  MediaWiki expects certain kinds of extensions to be implemented as subclasses of a MediaWiki-provided base class:
 *  – Subclasses of the class are used to build pages whose content is dynamically generated using a combination of the current system state, user input parameters, and database queries. Both reports and data entry forms can be generated. They are used for both reporting and administration purposes.
 *  – Skins change the look and feel of MediaWiki by altering the code that outputs pages by subclassing the MediaWiki class.
 *  – A technique for injecting custom PHP code at key points within MediaWiki processing. They are widely used by MediaWiki's parser, its localization engine, its extension management system, and its page maintenance system.
 *  – XML style tags that are associated with a php function that outputs HTML code. You do not need to limit yourself to formatting the text inside the tags. You don't even need to display it. Many tag extensions use the text as parameters that guide the generation of HTML that embeds Google objects, data entry forms, RSS feeds, excerpts from selected wiki articles.
 *  – A technique for mapping a variety of wiki text string to a single id that is associated with a function. Both variables and parser functions use this technique. All text mapped to that id will be replaced with the return value of the function. The mapping between the text strings and the id is stored in the array $magicWords. The interpretation of the id is a somewhat complex process – see  for more information.
 *  – Variables are something of a misnomer. They are bits of wikitext that look like templates but have no parameters and have been assigned hard-coded values. Standard wiki markup such as or  are examples of variables. They get their name from the source of their value: a php variable or something that could be assigned to a variable, e.g. a string, a number, an expression, or a function return value.
 *  – .  Similar to tag extensions, parser functions process arguments and returns a value. Unlike tag extensions, the result of parser functions is wikitext.
 *  – you can add custom modules to MediaWiki's action API, that can be invoked by JavaScript, bots or third-party clients.
 *  – If you need to store data in formats other than wikitext, JSON, etc. then you can create a new.

Support other core versions
There are two widespread conventions for supporting older versions of MediaWiki core:


 * Master: the master branch of the extension is compatible with as many old versions of core as possible. This results in a maintenance burden (backwards-compatibility hacks need to be kept around for a long time, and changes to the extension need to be tested with several versions of MediaWiki), but sites running old MediaWiki versions benefit from functionality recently added to the extension.
 * Release branches: release branches of the extension are compatible with matching branches of core, e.g. sites using MediaWiki need to use the  branch of the extension. (For extensions hosted on gerrit, these branches are automatically created when new versions of MediaWiki are released.) This results in cleaner code and faster development but users on old core versions do not benefit from bugfixes and new features unless they are backported manually.

Extension maintainers should declare with the  parameter of the Extension template which convention they follow.

发布
To autocategorize and standardize the documentation of your existing extension, please see. To add your new extension to this Wiki:

Deploying and registering
If you intend to have your extension deployed on Wikimedia sites (including possibly Wikipedia), additional scrutiny is warranted in terms of performance and security. Consult.

If your extension adds namespaces, you may wish to register its default namespaces; likewise, if it adds database tables or fields, you may want to register those at.

Please be aware that review and deployment of new extensions on Wikimedia sites can be extremely slow, and in some cases has taken more than two years.

Help documentation
You should provide public domain help documentation for features provided by your extension. is a good example. You should give users a link to the documentation via the function.

Providing support / collaboration
Extension developers should open an account on Wikimedia's, and request a new project for the extension. This provides a public venue where users can submit issues and suggestions, and you can collaborate with users and other developers to triage bugs and plan features of your extension.

参见

 * – implements some example features with extensive inline documentation
 * – a functioning boilerplate extension, useful as a starting point for your own extension
 * Read the Example extension, base your own code on the BoilerPlate extension.
 * cookiecutter-mediawiki-extension – a cookiecutter template which generates a boilerplate extension (with variables etc.)
 * cookiecutter-mediawiki-extension – a cookiecutter template which generates a boilerplate extension (with variables etc.)
 * Allows you to get going quickly with your own extension.
 * Can also generate the BoilerPlate extension.
 * - copy specific code from them
 * – explains how your extension can provide an API to clients
 * Best practices for extensions
 * Best practices for extensions
 * Best practices for extensions
 * Best practices for extensions