Difference between revisions of "Screen Plugins"

From EPrints Documentation
Jump to: navigation, search
m (syntax corrected)
 
(3 intermediate revisions by one other user 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 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.
  
 
==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]]
===To make a Screen for the Admin section===
+
  
  
 
See Also: [[List of Core Screen Plugins]]
 
See Also: [[List of Core Screen Plugins]]

Latest revision as of 10:05, 6 August 2019

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