Screen Plugins - Revision history

Drn@ecs.soton.ac.uk: Removed double redirect

2024-07-09T10:04:19Z

Removed double redirect

2019-08-06T10:05:51Z

syntax corrected

2010-04-15T09:54:19Z

2010-04-15T09:54:00Z

2010-04-15T07:54:21Z

2010-04-15T07:50:21Z

2010-04-14T09:41:26Z

‎The locations

2010-04-14T09:41:03Z

2010-04-14T07:20:54Z

2010-04-13T14:31:09Z

‎The locations

← Older revision		Revision as of 10:04, 9 July 2024
Line 12:		Line 12:


−	See Also: [[List of Core Screen Plugins]]	+	See Also: [[EPrints Directory Structure/eprints3/perl lib/EPrints/Plugin/Screen\|List of Core Screen Plugins]]

@@ 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:
-* 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.
 * Rights testing - the entire plugin, and individual actions, can be restricted in various ways.

@@ Line 8: / Line 8: @@
 ==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]]
+* [[How to make a Screen perform Actions]]
 See Also: [[List of Core Screen Plugins]]

@@ Line 9: / Line 9: @@
 ==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]]

← Older revision		Revision as of 07:54, 15 April 2010
Line 10:		Line 10:
	[[How to make a Screen for the Admin Section]]		[[How to make a Screen for the Admin Section]]

−	~~===To make a Screen for the Admin section===~~


	See Also: [[List of Core Screen Plugins]]		See Also: [[List of Core Screen Plugins]]

@@ Line 63: / Line 63: @@
 ====The locations====
-Where the link for the page appears is defined by <code>$self->{appears}->[''n'']->{place}</code> (in the <code>new</code> function.
+Where the link for the page appears is defined by <code>$self->{appears}->[''n'']->{place}</code> (in the <code>new</code> function.)
 We are defining a screen that appears in the "admin" area, and there are 4 tabs defined within the admin screen:

@@ Line 63: / Line 63: @@
 ====The locations====
-There are 4 tabs defined within the admin screen:
+Where the link for the page appears is defined by <code>$self->{appears}->[''n'']->{place}</code> (in the <code>new</code> function.
 * admin_actions_editorial
 * admin_actions_system
 * admin_actions_config
 * admin_actions_misc
 ===Making the page appear===

@@ 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: