Untitled


SUBMITTED BY: Guest

DATE: Oct. 18, 2024, 4:27 p.m.

FORMAT: Text only

SIZE: 3.0 kB

HITS: 119

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

comments powered by Disqus