1
|
|
|
<?php |
|
|
|
|
2
|
|
|
|
3
|
|
|
require_once __DIR__ . '/vendor/autoload.php'; |
4
|
|
|
|
5
|
|
|
use smtech\CanvasHack\Toolbox; |
6
|
|
|
use smtech\ReflexiveCanvasLTI\LTI\ToolProvider; |
7
|
|
|
use Battis\DataUtilities; |
8
|
|
|
|
9
|
|
|
define('CONFIG_FILE', __DIR__ . '/config.xml'); |
10
|
|
|
define('CANVAS_INSTANCE_URL', 'canvasInstanceUrl'); |
11
|
|
|
|
12
|
|
|
@session_start(); // TODO I don't feel good about suppressing warnings |
|
|
|
|
13
|
|
|
|
14
|
|
|
/* prepare the toolbox */ |
15
|
|
|
if (empty($_SESSION[Toolbox::class])) { |
16
|
|
|
$_SESSION[Toolbox::class] =& Toolbox::fromConfiguration(CONFIG_FILE); |
17
|
|
|
} |
18
|
|
|
$toolbox =& $_SESSION[Toolbox::class]; |
19
|
|
|
if (php_sapi_name() !== 'cli') { |
20
|
|
|
$toolbox->smarty_prependTemplateDir(__DIR__ . '/templates', basename(__DIR__)); |
|
|
|
|
21
|
|
|
$toolbox->smarty_assign([ |
|
|
|
|
22
|
|
|
'category' => DataUtilities::titleCase(preg_replace('/[\-_]+/', ' ', basename(__DIR__))) |
23
|
|
|
]); |
24
|
|
|
$smarty =& $toolbox->getSmarty(); // FIXME |
|
|
|
|
25
|
|
|
} |
26
|
|
|
|
27
|
|
|
/* |
28
|
|
|
* FIXME convience variables until plugins are all updated |
29
|
|
|
*/ |
30
|
|
|
$api =& $toolbox->getAPI(); |
31
|
|
|
$sql =& $toolbox->getMySQL(); |
32
|
|
|
$customPrefs =& $toolbox->getCustomPrefs(); |
|
|
|
|
33
|
|
|
|
34
|
|
|
/* set the Tool Consumer's instance URL, if present */ |
35
|
|
|
if (empty($_SESSION[CANVAS_INSTANCE_URL])) { |
36
|
|
|
if (!empty($_SESSION[ToolProvider::class]['canvas']['api_domain'])) { |
37
|
|
|
$_SESSION[CANVAS_INSTANCE_URL] = 'https://' . $_SESSION[ToolProvider::class]['canvas']['api_domain']; |
38
|
|
|
} else { |
39
|
|
|
$_SESSION[CANVAS_INSTANCE_URL] = $toolbox->config('TOOL_CANVAS_API')['url']; |
40
|
|
|
} |
41
|
|
|
} |
42
|
|
|
|
The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.
The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.
To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.