MediaWiki  1.32.5
SkinApi.php
Go to the documentation of this file.
1 <?php
31 class SkinApi extends SkinTemplate {
32  public $skinname = 'apioutput';
34 
35  public function getDefaultModules() {
36  $modules = parent::getDefaultModules();
37  $modules['styles']['skin'][] = 'mediawiki.skinning.interface';
38  return $modules;
39  }
40 
41  // Skip work and hooks for stuff we don't use
42 
43  function buildSidebar() {
44  return [];
45  }
46 
47  function getNewtalks() {
48  return '';
49  }
50 
51  function getSiteNotice() {
52  return '';
53  }
54 
55  public function getLanguages() {
56  return [];
57  }
58 
59  protected function buildPersonalUrls() {
60  return [];
61  }
62 
63  protected function buildContentNavigationUrls() {
64  return [];
65  }
66 
67  protected function buildNavUrls() {
68  return [];
69  }
70 }
SkinApi
SkinTemplate class for API output.
Definition: SkinApi.php:31
SkinApi\$template
$template
Definition: SkinApi.php:33
SkinApi\buildNavUrls
buildNavUrls()
build array of common navigation links
Definition: SkinApi.php:67
SkinApi\buildContentNavigationUrls
buildContentNavigationUrls()
a structured array of links usually used for the tabs in a skin
Definition: SkinApi.php:63
php
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php
Definition: injection.txt:35
SkinApi\buildPersonalUrls
buildPersonalUrls()
build array of urls for personal toolbar
Definition: SkinApi.php:59
SkinApi\getNewtalks
getNewtalks()
Gets new talk page messages for the current user and returns an appropriate alert message (or an empt...
Definition: SkinApi.php:47
SkinApi\buildSidebar
buildSidebar()
Build an array that represents the sidebar(s), the navigation bar among them.
Definition: SkinApi.php:43
SkinApi\$skinname
$skinname
Definition: SkinApi.php:32
$modules
$modules
Definition: HTMLFormElement.php:12
SkinApi\getSiteNotice
getSiteNotice()
Get the site notice.
Definition: SkinApi.php:51
SkinApi\getLanguages
getLanguages()
Generates array of language links for the current page.
Definition: SkinApi.php:55
SkinApi\getDefaultModules
getDefaultModules()
Defines the ResourceLoader modules that should be added to the skin It is recommended that skins wish...
Definition: SkinApi.php:35
class
you have access to all of the normal MediaWiki so you can get a DB use the etc For full docs on the Maintenance class
Definition: maintenance.txt:52
SkinTemplate
Base class for template-based skins.
Definition: SkinTemplate.php:38