Difference between revisions of "plugins"

From GeneWeb
Jump to navigation Jump to search
m (sommaire à droite)
m (mauvais lien interne)
Line 7: Line 7:
 
<!-- can there be several plugins locations?? to be verified -->
 
<!-- can there be several plugins locations?? to be verified -->
  
In addition, the [[gwf|{{c|.gwf}} parameters file]] must specify all the plugins to activate at launch through a single line where {{c|plugin#}} is the name of the desired plugin:
+
In addition, the [[configuration|{{c|.gwf}} parameters file]] must specify all the plugins to activate at launch through a single line where {{c|plugin#}} is the name of the desired plugin:
 
  plugins=plugin1,plugin2,plugin3
 
  plugins=plugin1,plugin2,plugin3
  

Revision as of 11:31, 7 September 2021

150px-Geographylogo svg.png Language:   English • français

GeneWeb offers a plugin mechanism since its version 7.1 that allows functional extensions without impacting the core operation of the system.

Plugins are loaded by gwd at launch time through the parameter -plugins (or -unsafe_plugins) pointing to the location of the plugins.

In addition, the .gwf parameters file must specify all the plugins to activate at launch through a single line where plugin# is the name of the desired plugin:

plugins=plugin1,plugin2,plugin3

Geneweb plugins

Carrousel (WIP)

Implements a carrousel display function for multiple images associated with a person. Provides the functions to upload and manage these images.

Cgl

The cgl plugin is an example of plugin whose function is limited to a post processing of the data produced by GeneWeb, removing in this data stream all occurrences of href. This plugin supersedes the cgl=on command one can add to the URL to ask for suppression of href links.

Export

Exports to .GED or .gw format the content of a base. Invoqued through a m=EXPORT command with the following parameters:

  • output=GED/GW select export format
  • spouses=on/off
  • parents=on/off
  • children=on/off
  • notes=/nn/nnn
  • sources=on/off
  • isolated=on/off
  • pictures=on/off
  • isolated=on/off

{…}

Forum

Isolate in a plugin the forum functions.

No index

Implements the opt=no_index parameter in the URL. Replaces non stable instances of i=index by their stable values p=first_name;n=surname;oc=occ.

V7

The v7 plugin regroups in a single place the traditional V7 behavior of GeneWeb (over time a V8 plugin may offer a new set of templates). All GUI related informations that were located in the hd repository folder are now located in plugins/v7/assets.

Several .ml files (cousins, date, descend, interp, perso, place, some, sosa, srcfile, templ) implement slight (or significant) variations from the core GeneWeb behavior. The following new commands are implemented in this plugin:

  • m=A;t=FC displays ancestry of a person in fan-chart format.
  • m=C;v1=x;v2=y computes number of “cousins” x levels up and y level down and draws a table of existing kinships.
  • m=D prints descendants lists or tables using v7 template interpretor.
  • m=DOC operates as m=SRC with additional .html and .pdf formats. Allows files to be stored in sub-folders
  • m=L prints a list of persons (used with the m=PS command below).
  • m=P prints the list of persons with a given first_name, with additional options.
  • m=PS prints the list of surnames associated with a place for a given set of events (birth, baptism, marriage, death, burial).

V7 images

Isolates in a plugin the image manipulations functions.

{…}

Welcome (WIP)

This plugin inverts the order of the two data entry lines for the search of the welcome page, and proposes some additional behaviors during this search.

XHTML

{…}

Development of plugins

Developers should explore existing plugins to infer the overall mechanism, but it should be noted that such development requires a good understanding of both the OCaml language and GeneWeb itself.

Developers will find plugins in the plugins folder of the GitHub repository. In the plugins folder, each plugin is in a subfolder named pl_name_plugin. The command make distrib will compile those plugins and install then in a distribution/plugin folder.

Associated ressources with each plugins, such as templates, images, lexicon entries, are located in an assets subfolder.