Changes

# [[Contact#Mailing_listsAnnounce_it_on_the_Gramps_mailing_list|Announce it on the Gramps mailing list]] - Let users know it exist and how to use it.

Follow the development API for your tool, [[Report-writing_tutorial|report]], view, or [[Gramplets]]. Place all of your associated .py, .glade, etc. files in this directory. For general information on Gramps development see [[Portal:Developers]] and [[Writing a plugin|Writing a Plugin]] specifically.

To test your addon as you develop it is suggested that you insert copy your NewProjectName plugin into your Gramps user plugin directory with a link to from your addon development directory, like so: prior to testing. cd ~/Or just edit in the Gramps user plugin directory until it is ready to publish, then copy back to your addon development directory.gramps/gramps51/plugins ln -s ~/addons-source/NewProjectName NewProjectName

The application programming interface or API for reports is treated at [[Report-writing_tutorial]]. For general information on Gramps development see [[Portal:Developers]] and [[Writing a plugin|Writing a Plugin]] specifically.

{{man note|Note:|Running the command '''<code>make.py xxx build''' </code> will increment the third number in your dotted version number of all addons in the <code>*.gpr.py </code> file. Consider this number to be a "build number".}}

{{man warn|Gramps needs to have been built|Make sure you have already built gramps51 or master. Change to the appropriate git branch in your gramps directory, and run '<code>python3 setup.py build' </code> See [[Linux:Build_from_source]]}}

===List your addon===Add a short description of your addon to the Addons list by editing the current release listing eg: [[5.1_Addons]] or if the addon is meant for a future release [[5.2_Addons]] when available. ==== Example addon template ====Examine the listing for other addons and refer to the [[Plugin list legend]] for details of on the meaning of each columns.<pre>|- <!-- Copy this section and list your Addon -->|<!-- Plugin / Documentation -->|<!-- Type -->|<!-- Image -->|<!-- Description -->|<!-- Use -->|<!-- Rating (out of 4) -->|<!-- Contact -->|<!-- Download -->|-</pre> ===Document your addon===Document the addon in the wiki using the page name format of {{man menu|Addon:NewProjectName}} examine the other addon support pages for the general format to use. ({{man tip|Hint:on creating a new wiki page.|To create a new wiki page use the search box to search for the name of your page that doesn't exist then on the search results page you will be provided with a link to create the new page, by selecting and you can add your content, examine }} ====Example addon article====Consider including the following information: <pre><!-- Copy this section to your Addon support page-->{{Third-party plugin}}<!-- This is a mediawiki template that expands out to display the other standard addon support pages for message you see at the general format to use.)top of each addon page--> <!--sections only add if needed-->== Usage ==

== Miscellaneous commands Features==

To compile translations for all projects <!--default categories-->[[Category:Addons]][[Category:Plugins]][[Category:Developers/General]]</pre>

: <code>python3 make== Announce it on the Gramps mailing list ==Join the [[Contact#Mailing_lists|Gramps Mailing lists]] and announce it to the users with general information on why you created and how to use it.py gramps51 compile all</code>

Become a team member user on the [https://gramps-project.org/bugs/view_all_bug_page.php Gramps MantisBT (Mantis BugTracker)].

Users tend to not understand coding and they make assumptions. So be kindly mentoring kind and guiding if a report is ambiguous or inaccurate. A dismissive or condescending negative remark from a an addon developer or anyone can be very damagingdiscouraging.