Untitled


SUBMITTED BY: Guest

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

FORMAT: Text only

SIZE: 3.0 kB

HITS: 76

  1. <?php
  2. echo "tes";
  3. /**
  4. * @mainpage OJS API Reference
  5. *
  6. * Welcome to the OJS API Reference. This resource contains documentation
  7. * generated automatically from the OJS source code.
  8. *
  9. * The design of Open %Journal Systems 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 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, Articles, and Journals;
  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. * Additionally, many of the concerns shared by multiple PKP applications are
  34. * implemented in the shared "pkp-lib" library, shipped in the lib/pkp
  35. * subdirectory. The same conventions listed above apply to lib/pkp as well.
  36. *
  37. * As the system makes use of inheritance and has consistent class naming
  38. * conventions, it is generally easy to tell what category a particular class
  39. * falls into.
  40. *
  41. * For example, a Data Access Object class always inherits from the DAO class,
  42. * has a Class name of the form [Something]%DAO, and has a filename of the form
  43. * [Something]%DAO.inc.php.
  44. *
  45. * To learn more about developing OJS, there are several additional resources
  46. * that may be useful:
  47. * - The docs/README.md document
  48. * - The PKP support forum at https://forum.pkp.sfu.ca/
  49. * - Documentation available at https://docs.pkp.sfu.ca/dev/
  50. *
  51. * @file ojs/index.php
  52. *
  53. * Copyright (c) 2014-2021 Simon Fraser University
  54. * Copyright (c) 2003-2021 John Willinsky
  55. * Distributed under the GNU GPL v3. For full terms see the file docs/COPYING.
  56. *
  57. * @ingroup index
  58. *
  59. * Bootstrap code for OJS site. Loads required files and then calls the
  60. * dispatcher to delegate to the appropriate request handler.
  61. */
  62. // Initialize global environment
  63. define('INDEX_FILE_LOCATION', __FILE__);
  64. $application = require('./lib/pkp/includes/bootstrap.inc.php');
  65. // Serve the request
  66. $application->execute();

comments powered by Disqus