MediaWiki  1.32.5
generateRandomImages.php
Go to the documentation of this file.
1 <?php
8 // Start up MediaWiki in command-line mode
9 require_once __DIR__ . "/../../../../maintenance/Maintenance.php";
10 require __DIR__ . "/RandomImageGenerator.php";
11 
13 
14  public function getDbType() {
15  return Maintenance::DB_NONE;
16  }
17 
18  public function execute() {
19  $getOptSpec = [
20  'dictionaryFile::',
21  'minWidth::',
22  'maxWidth::',
23  'minHeight::',
24  'maxHeight::',
25  'shapesToDraw::',
26  'shape::',
27 
28  'number::',
29  'format::'
30  ];
31  $options = getopt( null, $getOptSpec );
32 
33  $format = $options['format'] ?? 'jpg';
34  unset( $options['format'] );
35 
36  $number = isset( $options['number'] ) ? intval( $options['number'] ) : 10;
37  unset( $options['number'] );
38 
39  $randomImageGenerator = new RandomImageGenerator( $options );
40  $randomImageGenerator->writeImages( $number, $format );
41  }
42 }
43 
44 $maintClass = 'GenerateRandomImages';
GenerateRandomImages\getDbType
getDbType()
Does the script need different DB access? By default, we give Maintenance scripts normal rights to th...
Definition: generateRandomImages.php:14
RUN_MAINTENANCE_IF_MAIN
require_once RUN_MAINTENANCE_IF_MAIN
Definition: maintenance.txt:50
Maintenance
Abstract maintenance class for quickly writing and churning out maintenance scripts with minimal effo...
Definition: maintenance.txt:39
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
RandomImageGenerator
RandomImageGenerator: does what it says on the tin.
Definition: RandomImageGenerator.php:30
GenerateRandomImages
Definition: generateRandomImages.php:12
$maintClass
$maintClass
Definition: generateRandomImages.php:44
Maintenance\DB_NONE
const DB_NONE
Constants for DB access type.
Definition: Maintenance.php:65
GenerateRandomImages\execute
execute()
Do the actual work.
Definition: generateRandomImages.php:18
$options
null means default in associative array with keys and values unescaped Should be merged with default with a value of false meaning to suppress the attribute in associative array with keys and values unescaped & $options
Definition: hooks.txt:2044