Screen Plugins: Difference between revisions
No edit summary |
Removed double redirect |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
Screen Plugins are used to handle the User Interface. Screen plugins provide the UI to the user-interaction parts of EPrints. A screen plugin can include: | Screen Plugins are used to handle the User Interface. Screen plugins provide the UI to the user-interaction parts of EPrints. A screen plugin can include: | ||
* A render | * A render - several pages (like a search) or none (like the eprint move plugin). Most have a single page of output. | ||
* Actions - things which modify the system in some way. | * Actions - things which modify the system in some way. | ||
* Rights testing - the entire plugin, and individual actions, can be restricted in various ways. | * Rights testing - the entire plugin, and individual actions, can be restricted in various ways. | ||
==Making Screens== | ==Making Screens== | ||
[[How to make a Screen for the Admin Section]] | * [[How to make a Screen for the Admin Section]] | ||
* [[How to make a Screen perform Actions]] | |||
See Also: [[EPrints Directory Structure/eprints3/perl lib/EPrints/Plugin/Screen|List of Core Screen Plugins]] | |||
See Also: [[List of Core Screen Plugins]] | |||
Latest revision as of 10:04, 9 July 2024
Screen Plugins are used to handle the User Interface. Screen plugins provide the UI to the user-interaction parts of EPrints. A screen plugin can include:
- A render - several pages (like a search) or none (like the eprint move plugin). Most have a single page of output.
- Actions - things which modify the system in some way.
- Rights testing - the entire plugin, and individual actions, can be restricted in various ways.
Making Screens
See Also: List of Core Screen Plugins