Manual:Developing extensions/pl



Każde rozszerzenie posiada 3 części:


 * 1) Ustawienie
 * 2) Wykonanie
 * 3) Lokalizacja

Minimalistyczne rozszerzenie zawiera 3 pliki, po jednym na każdą część:


 * MyExtension/extension.json: Zawiera instrukcje do ustawienia. Plik musi się nazywać extension.json. (Przed MediaWiki 1.25 instrukcje ustawiania byly w pliku  nazwanym po nazwie rozszerzenia Wiele rozszerzeń wciąż ma podkładki kompatybilności z wcześniejszymi wersjami w tym pliku PHP.
 * MyExtension/MyExtension_body.php: Przechowuje kod wykonywania dla rozszerzenia. Nazwa MyExtension_body.php jest konwencjonalna, ale nie jest wymagana. Jeżeli twoje rozszerzenie jest zaawansowane i posiada wiele plików PHP, powinieneś/aś zgodnie z konwencją i dać kod inplementacji w podfolderze o nazwie (Example i BoilerPlate nie podążają za tą konwencją). Na przykład, zobacz rozszerzenie.
 * MyExtension/i18n/*.json: Przechowuje informacje o lokalizacje dla rozszerzenie.

Kiedy tworzysz rozszerzenie, zastąp "MyExstension" nazwą swojego rozszerzenia. Używaj nazw UpperCamelCase dla nazwy jego folderu i pliku/ów PHP; to jest konwencja nazywania plików. (The is a good starting point for your extension. You can also consider using MWStew for generating your extension boilerplate. Also check out the cookiecutter template for MediaWiki extensions on GitHub.)

Trzy części rozszerzenia, ustawianie, wykonywanie i lokalizacja tak samo jak typy rozszerzeń i  licencjonowanie i  publikowanie są opisane w następujących sekcjach tej strony.

Ustawianie
Your goal in writing the setup portion is to consolidate set up so that users installing your extension need do nothing more than include the setup file in their file, like this:

If you want to make your extension user configurable, you need to define and document some configuration parameters and your users' setup should look something like this:

To reach this simplicity, your setup file needs to accomplish a number of tasks (described in detail in the following sections):


 * register any media handler, parser function, special page, custom XML tag, and variable used by your extension.
 * define and/or validate any configuration variables you have defined for your extension.
 * prepare the classes used by your extension for autoloading
 * determine what parts of your setup should be done immediately and what needs to be deferred until the MediaWiki core has been initialized and configured
 * define any additional hooks needed by your extension
 * create or check any new database tables required by your extension.
 * set up localisation for your extension

Rejestrowanie cech z MediaWiki
MediaWiki lists all the extensions that have been installed on its  page. For example, you can see all the extensions installed on this wiki at Special:Version. It is good form to make sure that your extension is also listed on this page. To do this, you will need to add an entry to for each media handler, parser function, special page, custom XML tag, and variable used by your extension. The entry will look something like this:

See for full details on what these fields do. Many of the fields are optional, but it's still good practice to fill them out. The  refers to the version of the schema the  file is written against. As of now the only supported version is 1 (MediaWiki 1.26.x and 1.27.x).

In addition to the above registration, you must also "hook" your feature into MediaWiki. The above only sets up the Special:Version page. The way you do this depends on the type of your extension. For details, please see the documentation for each type of extension:

Robienie twojego rozszerzenia możliwego do konfiguracji przez użytkownika
If you want your user to be able to configure your extension, you'll need to provide one or more configuration variables. It is a good idea to give those variables a unique name. They should also follow MediaWiki naming conventions (e.g. global variables should begin with $wg).

For example, if your extension is named "Very silly extension that does nothing", you might want to name all your configuration variables to begin  or. It doesn't really matter what you choose so long as none of the MediaWiki core begins its variables this way and you have done a reasonable job of checking to see that none of the published extensions begin their variables this way. Users won't take kindly to having to choose between your extension and some other extensions because you chose overlapping variable names.

It is also a good idea to include extensive documentation of any configuration variables in your installation notes.

Here is an example boiler plate that can be used to get started:

Przygotowanie klas do autokonfiguracji
If you choose to use classes to implement your extension, MediaWiki provides a simplified mechanism for helping PHP find the source file where your class is located. In most cases this should eliminate the need to write your own  method.

To use MediaWiki's autoloading mechanism, you add entries to the field. The key of each entry is the class name; the value is the file that stores the definition of the class. For a simple one class extension, the class is usually given the same name as the extension, so your autoloading section might look like this (extension is named MyExtension):

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

Definiowanie dodatkowych haczyków
Zobacz.

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

Ustawianie lokalizacji
Zobacz:
 * Localisation (summary)
 * Localisation (detailed)
 * Namespaces

Dodawanie logów
On MediaWiki, all actions by users on wiki are tracked for transparency and collaboration. Zobacz by wiedzieć jak to zrobić.

Wykonywanie
The technique for writing the implementation portion depends upon the part of MediaWiki system you wish to extend:
 * Wiki markup: Extensions that extend wiki markup will typically contain code that defines and implements custom XML tags, parser functions and variables.
 * Reporting and administration: Extensions that add reporting and administrative capabilities usually do so by adding special pages. Aby uzyskać więcej informacji, zobacz.
 * Article automation and integrity: Extensions that improve the integration between MediaWiki and its backing database or check articles for integrity features, will typically add functions to one of the many hooks that affect the process of creating, editing, renaming, and deleting articles. For more information about these hooks and how to attach your code to them, please see.
 * Look and feel: Extensions that provide a new look and feel to MediaWiki are bundled into skins. For more information about how to write your own skins, see and.
 * Bezpieczeństwo: Extensions that limit their use to certain users should integrate with MediaWiki's own permissions system. To learn more about that system, please see . Some extensions also let MediaWiki make use of external authentication mechanisms. Aby uzyskać więcej informacji, zobacz . In addition, if your extension tries to limit readership of certain articles, please check out the gotchas discussed in.

Zobacz też  oraz.

Lokalizacja
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.

Przechowywanie komunikatu w .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. An example you can find e.g. in extension MobileFrontend. Here is an example of a minimal JSON file (in this case en.json:

en.json

Przechowywanie dokumentacji komunikatu w 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:

Definiowanie komunikatu

 * Assign each message a unique, lowercase, no space message id; e.g.uploadwizard-desc
 * For any text string displayed to the user, define a message.
 * MediaWiki supports parameterized messages and that feature should be used when a message is dependent on information generated at runtime. Parameter placeholders are specified with $n, where n represents the index of the placeholder; e.g.

Definiowanie documentacji komunikatu
Each message you define needs to have an associated message documentation entry Message documentation; in qqq.json e.g.

Ładowanie pliku lokalizacyjnego
In your setup routine, define the location of your messages files (e.g. in directory i18n/):

Używanie wfMessage w 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. Przykład:

Używanie mw.message w JavaScript
It's possible to use i18n functions in JavaScript too. Zobacz po szczegóły.

Rodzaje rozszerzeń
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.

Wspieranie innych wersji jądra
There are two widespread conventions for supporting older versions of MediaWiki core:

Extension maintainers should declare with the  parameter of the Extension template which convention they follow.
 * 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 1.27 need to use the REL1_27 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.

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

Deploying and registering
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.

Dokumentacja pomocy
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.

Zobacz też

 * – 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 template for the python tool cookiecutter to generate a boilerplate extension (with variables etc.)
 * Allow 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
 * Best practices for extensions