How to write plugins - Revision history

Dkane: /* You will need */

2015-11-02T16:12:37Z

‎You will need

2015-11-02T16:06:12Z

‎You will need

2012-05-03T15:20:54Z

‎Screen Plugin: - adding links to the existing tutorials, I didn't know they existed.

2010-02-12T11:25:04Z

‎You will need

2010-02-12T11:24:16Z

‎You will need

2010-02-11T10:45:05Z

‎Write a Plugin!

2010-02-11T10:41:37Z

2010-02-11T10:10:23Z

‎What next

2010-02-11T09:31:15Z

‎What next

2010-02-11T09:29:15Z

‎What next

@@ Line 9: / Line 9: @@
 == You will need ==
-* A basic understanding of perl (don't be scared - its not hard and there's plenty of tutorials on the web)
+* A basic understanding of perl (don't be scared - its not hard and there are plenty of tutorials on the web)
 * An EPrints installation to play about on. A Virtual box with [[:Category:Installation|EPrints installed]] is ideal.

@@ Line 9: / Line 9: @@
 == You will need ==
-* A basic understanding of perl (dont be scared - its not hard and theres plenty of tutorials on the web)
+* A basic understanding of perl (don't be scared - its not hard and there's plenty of tutorials on the web)
 * An EPrints installation to play about on. A Virtual box with [[:Category:Installation|EPrints installed]] is ideal.

← Older revision		Revision as of 15:20, 3 May 2012
Line 62:		Line 62:

	Look at the existing Screen Plugins for an idea of how they work. They can be very simple.		Look at the existing Screen Plugins for an idea of how they work. They can be very simple.
		+
		+	* [[How to make a Screen for the Admin Section]]
		+	* [[How to make a Screen perform Actions]]

	==== Input Component Plugin ====		==== Input Component Plugin ====

@@ Line 15: / Line 15: @@
 * Information from the [[:Category:API|EPrints API]]
-* For some types of plugin you might also need some Javascript and CSS knowledge
+* For some types of plugin you might also find some Javascript and CSS knowledge helpful.
 == Write a Plugin! ==

@@ Line 11: / Line 11: @@
 * A basic understanding of perl (dont be scared - its not hard and theres plenty of tutorials on the web)
-* An EPrints installation to play about on. A Virtual box with [[:Catagory:Installation|EPrints installed]] is ideal.
+* An EPrints installation to play about on. A Virtual box with [[:Category:Installation|EPrints installed]] is ideal.
 * Information from the [[:Category:API|EPrints API]]

@@ Line 67: / Line 67: @@
 These handle how the workflow components are rendered. Built in components include the default (one field) component, the multiple fields component, the upload component, the subject component (which does pretty things to a field of type "subject") and the XHTML component. You can add your own or sub-class existing ones.
-===== Convert Plugin =====
+==== Convert Plugin ====
 These are used for two things, currently.

@@ Line 82: / Line 82: @@
 == What next ==
 Try out some of the examples and see where you get to. If you hit problems you can always talk to EP-Tech. {{EPrintsTech}}.
 Its probably a good a idea to look at [[Tips to write plugins|some tips]]. It will help you write better plugins.
 If you've written a plugin and you're happy with it the EPrints Team encourages you to share it with the EPrints community at [http://files.eprints.org http://files.eprints.org]. If nothing else its a good place to store your code for future use. You might even get some valuable feed back.

← Older revision		Revision as of 09:31, 11 February 2010
Line 85:		Line 85:
	If you are stuggling to fit your functionality into a plugin you might want to look at [[Tips to write plugins\|some tips]].		If you are stuggling to fit your functionality into a plugin you might want to look at [[Tips to write plugins\|some tips]].

−	If you've written a plugin and you're happy with it the EPrints Team encourages you to share it with the EPrints community at [http://files.eprints.org http://files.eprints.org].	+	If you've written a plugin and you're happy with it the EPrints Team encourages you to share it with the EPrints community at [http://files.eprints.org http://files.eprints.org]. If nothing else its a good place to store your code for future use. You might even get some valuable feed back.

@@ Line 81: / Line 81: @@
 == What next ==
-Try out some of the examples and see where you get to. If you hit problems you can always talk to EP-Tech {{EPrintsTech}}.
+Try out some of the examples and see where you get to. If you hit problems you can always talk to EP-Tech. {{EPrintsTech}}.
 If you are stuggling to fit your functionality into a plugin you might want to look at [[Tips to write plugins|some tips]].
-If you've written a plugin and you're happy with it the EPrints Team encourages you to share it with the EPrints community at [http://files.eprints.org|http://files.eprints.org].
+If you've written a plugin and you're happy with it the EPrints Team encourages you to share it with the EPrints community at [http://files.eprints.org http://files.eprints.org].