|
1 | 1 | <?php
|
2 | 2 |
|
3 | 3 | /**
|
4 |
| - * @mainpage OMP API Reference |
5 |
| - * |
6 |
| - * Welcome to the OMP API Reference. This resource contains documentation |
7 |
| - * generated automatically from the OMP source code. |
8 |
| - * |
9 |
| - * The design of Open %Monograph press is heavily structured for |
10 |
| - * maintainability, flexibility and robustness. Those familiar with Sun's |
11 |
| - * Enterprise Java Beans technology or the Model-View-Controller (MVC) pattern |
12 |
| - * will note many similarities. |
13 |
| - * |
14 |
| - * As in a MVC structure, data storage and representation, user interface |
15 |
| - * presentation, and control are separated into different layers. The major |
16 |
| - * categories, roughly ordered from "front-end" to "back-end," follow: |
17 |
| - * - Smarty templates, which are responsible for assembling HTML pages to |
18 |
| - * display to users; |
19 |
| - * - Page classes, which receive requests from users' web browsers, delegate |
20 |
| - * any required processing to various other classes, and call up the |
21 |
| - * appropriate Smarty template to generate a response; |
22 |
| - * - Controllers, which implement reusable pieces of content e.g. for AJAX |
23 |
| - * subrequests. |
24 |
| - * - Action classes, which are used by the Page classes to perform non-trivial |
25 |
| - * processing of user requests; |
26 |
| - * - Model classes, which implement PHP objects representing the system's |
27 |
| - * various entities, such as Users, Monographs, and Presses; |
28 |
| - * - Data Access Objects (DAOs), which generally provide (amongst others) |
29 |
| - * update, create, and delete functions for their associated Model classes, |
30 |
| - * are responsible for all database interaction; |
31 |
| - * - Support classes, which provide core functionalities, miscellaneous common |
32 |
| - * |
33 |
| - * As the system makes use of inheritance and has consistent class naming |
34 |
| - * conventions, it is generally easy to tell what category a particular class |
35 |
| - * falls into. |
36 |
| - * For example, a Data Access Object class always inherits from the DAO class, |
37 |
| - * has a Class name of the form [Something]%DAO, and has a filename of the form |
38 |
| - * [Something]%DAO.inc.php. |
39 |
| - * |
40 |
| - * To learn more about developing OMP, there are several additional resources |
41 |
| - * that may be useful: |
42 |
| - * - The docs/README document |
43 |
| - * - The PKP support forum at https://forum.pkp.sfu.ca |
44 |
| - * - Documentation available at https://docs.pkp.sfu.ca/dev/ |
45 |
| - * |
46 | 4 | * @file index.php
|
47 | 5 | *
|
48 | 6 | * Copyright (c) 2014-2021 Simon Fraser University
|
49 | 7 | * Copyright (c) 2003-2021 John Willinsky
|
50 | 8 | * Distributed under the GNU GPL v3. For full terms see the file docs/COPYING.
|
51 | 9 | *
|
52 |
| - * @ingroup index |
53 |
| - * |
54 | 10 | * Bootstrap code for OMP site. Loads required files and then calls the
|
55 | 11 | * dispatcher to delegate to the appropriate request handler.
|
56 | 12 | */
|
|
0 commit comments