Writing a plugin - Revision history

Patsyblefebre: 3.2 and later

2013-02-01T04:32:27Z

3.2 and later

2013-02-01T04:05:32Z

‎Test it: pylint

2013-02-01T04:04:39Z

‎Write it: x

2013-02-01T03:09:17Z

‎Pitfalls: considerations

2013-01-17T01:01:04Z

Gramps

2013-01-17T00:52:54Z

Gramps

2012-12-26T22:16:30Z

‎Share it: update link

2012-09-08T10:46:36Z

‎Share it

2012-03-02T20:11:34Z

‎Write it

2011-09-28T02:10:35Z

‎Share it

@@ Line 3: / Line 3: @@
 To get started writing a plugin, please see the following tutorials:
-* [[Addons development]] - for Gramps version 3.x
+* [[Addons development]] - for Gramps version 3.2 and later
 * [[Gramplets]]
 * [[Quick Views]]

@@ Line 19: / Line 19: @@
 * See [[Unit_Test_Quickstart|Unit Test Quickstart]]
-* Check syntax issues with [http://gramps-project.org/wiki/index.php?title=Programming_Guidelines#Pylint pylint]
+* Check syntax issues with [[Programming_Guidelines#Pylint|Pylint]]
 There is some samples of tests for localized [[Relationship_Calculator#Tests|Relationships calculators]] or [[Date_Handler#How_to_test_a_date_handler_for_your_locale|Date handlers]]:

@@ Line 3: / Line 3: @@
 To get started writing a plugin, please see the following tutorials:
-* [[Addons development]] - for Gramps version 3.2/3.3
+* [[Addons development]] - for Gramps version 3.x
 * [[Gramplets]]
 * [[Quick Views]]

@@ Line 69: / Line 69: @@
 Also, have a look at [[Coding_for_translation#Tips_for_writing_a_translatable_report|Coding for translation]].
-==== Pitfalls ====
+==== Considerations ====
 * We support right to left languages like Arabic, so never constructs text parts by concatenation of pieces. Always use full sentences/paragraphs with variable substitution, so that a right to left language can translate it correctly.

@@ Line 12: / Line 12: @@
 * [[Simple Access API]]
 * [[Using database API]]
-* [[Getting started with GRAMPS development]]
+* [[Getting started with Gramps development]]
 * [[Report_API|Report API]]
 * [[Report_Generation|Report Generation]]

@@ Line 8: / Line 8: @@
 * [[Report-writing tutorial]]
-For more general GRAMPS development information, see:
+For more general Gramps development information, see:
 * [[Simple Access API]]
@@ Line 53: / Line 53: @@
 == Share it==
-Have you written a plugin for GRAMPS you want to share with the world? Here's how you do it:
+Have you written a plugin for Gramps you want to share with the world? Here's how you do it:
-* Add the correct license. GRAMPS is GPLv2, you use the GRAMPS plugin system, so make sure you have the correct license at the top of your file. See [[Howto: Contribute to GRAMPS]]
+* Add the correct license. Gramps is GPLv2, you use the Gramps plugin system, so make sure you have the correct license at the top of your file. See [[Howto: Contribute to Gramps]]
 * Create a filename.tar.gz or filename.zip file of your plugin code
 * Upload the code to this wiki
@@ Line 72: / Line 72: @@
 * We support right to left languages like Arabic, so never constructs text parts by concatenation of pieces. Always use full sentences/paragraphs with variable substitution, so that a right to left language can translate it correctly.
 [[Category:Developers/General]]
-[[Category:Developers/General]] [[Category:Plugins]] [[Category:Developers/Tutorials]]
+[[Category:Plugins]]

@@ Line 58: / Line 58: @@
 * Create a filename.tar.gz or filename.zip file of your plugin code
 * Upload the code to this wiki
-* Add an entry of your plugin to [[Plugins3.4]]. See [[Plugin list legend]] for meaning of columns. Please use these meanings and pay attention to details; this page is machine readable.
+* Add an entry of your plugin to [[Plugins4.0]]. See [[Plugin list legend]] for meaning of columns. Please use these meanings and pay attention to details; this page is machine readable.
 * Create a new wiki page, and refer to that page here, with a short description of what the plugin does