Difference between revisions of "Screen Plugins"

From EPrints Documentation
Jump to: navigation, search
(Removed double redirect)
 
(17 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:Configuration]]
+
[[Category:Howto]]
[[Category:Rubbish]]
+
[[Category:Plugins]]
 
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 screen plugin can actually have several pages (like a search) or none (like the eprint move plugin). Most have a single page of output.
+
* 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.
  
See Also: [[List of Core Screen Plugins]]
+
==Making Screens==
 +
* [[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]]

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