MediaWiki  master
DateTimeInputWidget.php
Go to the documentation of this file.
1 <?php
2 
3 namespace MediaWiki\Widget;
4 
6 
13 class DateTimeInputWidget extends \OOUI\InputWidget {
14 
15  protected $type = null;
16  protected $min = null;
17  protected $max = null;
18  protected $clearable = null;
19 
27  public function __construct( array $config = [] ) {
28  // We need $this->type set before calling the parent constructor
29  if ( isset( $config['type'] ) ) {
30  $this->type = $config['type'];
31  } else {
32  throw new \InvalidArgumentException( '$config[\'type\'] must be specified' );
33  }
34 
35  parent::__construct( $config );
36 
37  // Properties, which are ignored in PHP and just shipped back to JS
38  if ( isset( $config['min'] ) ) {
39  $this->min = $config['min'];
40  }
41  if ( isset( $config['max'] ) ) {
42  $this->max = $config['max'];
43  }
44  if ( isset( $config['clearable'] ) ) {
45  $this->clearable = $config['clearable'];
46  }
47 
48  // Initialization
49  $this->addClasses( [ 'mw-widgets-datetime-dateTimeInputWidget' ] );
50  }
51 
52  protected function getJavaScriptClassName() {
53  return 'mw.widgets.datetime.DateTimeInputWidget';
54  }
55 
56  public function getConfig( &$config ) {
57  $config['type'] = $this->type;
58  if ( $this->min !== null ) {
59  $config['min'] = $this->min;
60  }
61  if ( $this->max !== null ) {
62  $config['max'] = $this->max;
63  }
64  if ( $this->clearable !== null ) {
65  $config['clearable'] = $this->clearable;
66  }
67  return parent::getConfig( $config );
68  }
69 
70  protected function getInputElement( $config ) {
71  return ( new Tag( 'input' ) )->setAttributes( [ 'type' => $this->type ] );
72  }
73 }
The wiki should then use memcached to cache various data To use multiple just add more items to the array To increase the weight of a make its entry a array("192.168.0.1:11211", 2))
Config $config
Definition: MediaWiki.php:43
Apache License January AND DISTRIBUTION Definitions License shall mean the terms and conditions for use
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
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN type
Definition: postgres.txt:22