Difference between revisions of "Screen Plugins"
| (16 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:Howto]] | ||
| + | [[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: | ||
| Line 4: | Line 6: | ||
* 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== | ||
| + | * [[How to make a Screen for the Admin Section]] | ||
| + | * [[How to make a Screen perform Actions]] | ||
| + | |||
See Also: [[List of Core Screen Plugins]] | See Also: [[List of Core Screen Plugins]] | ||
Revision as of 09:54, 15 April 2010
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.
- 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
