g2:choosing
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
g2:choosing [2011/01/12 09:17] – [Rationale for G2 specificities] fgm | g2:choosing [2023/05/27 16:05] (current) – fgm | ||
---|---|---|---|
Line 1: | Line 1: | ||
Back to [[g2: | Back to [[g2: | ||
+ | ====== Choosing a glossary-type module ====== | ||
+ | As of 2011, none of the glossary modules is intended as a plug-in replacement for the original glossary module already available with drupal since its humble beginnings. Each of the alternatives was designed for slightly different needs, and this page is here to help you choose which module you should probably be using, or if you should really write your own. Lexicon evolved from glossary to accomodate yet another set of requirements, | ||
+ | Left-to-right order by date of creation. Empty cells means info not yet available. Please contribute ! | ||
+ | TODO: import " | ||
+ | * The [[http:// | ||
+ | * The [[http:// | ||
- | ====== Choosing a glossary-type module ====== | + | ^ Feature |
- | + | ^ Drupal-related | |
- | G2 is not intended as a direct replacement for the glossary module already available with drupal for quite some time now. It was designed for slightly different needs, and this page is here to help you choose which module you should probably be using, or if you should really write your own. Lexicon has been evolved from glossary to accomodate yet another set of requirements, | + | | Maintenance |
- | + | | Drupal | |
- | ^ Feature | + | | Drupal 9.x | No | -dev | Yes | No | |
- | ^ Drupal-related | + | | Drupal 8.x |
- | | Drupal | + | | Drupal |
- | | Drupal | + | | Drupal 6.x | Yes | Yes | Yes |
- | | Drupal 5.x | Yes | + | | Drupal 5.x |
- | | Drupal 4.7.x | Yes | + | | Drupal 4.7.x |
- | | Drupal 4.6.x | Yes | + | | Drupal 4.6.x |
- | | AJAX | No | Some autocompletion | + | | Earlier Drupal versions |
- | | Storage | + | | AJAX | No | Some autocompletion | | | |
- | ^ Services provided | + | | Storage |
- | | multiple glossaries on one site | + | | Revision support |
- | | RSS feeds on entries | + | | Simpletest |
- | | RSS feeds on additional vocabularies | No | + | ^ Services provided |
- | | classify entries | + | | multiple glossaries on one site |
- | | commenting on entries | + | | RSS feeds on entries |
- | | private editorial information | + | | RSS feeds on additional vocabularies | No |
- | | alphabar maintenance | + | | classify entries |
- | | content filtering, automatic | + | | commenting on entries |
- | | content filtering, explicit | + | | private editorial information |
- | | feature blocks | + | | alphabar maintenance |
- | | remote glossaries | + | | remote glossaries |
- | | Security | + | | steganographic content protection | | No | |
- | ^ 3rd party integration | + | | RDF information |
- | | [[http:// | + | ^ i18n ^ Glossary |
- | | Views: basic | core | core + specific | + | | Translation template supplied |
- | | Views: default views | No | No | | + | | Multilingual blocks |
- | | [[http:// | + | | Translatable |
- | | [[http:// | + | ^ Feature blocks |
- | ^ Performance | + | | Alphabar |
- | | memory needs/ | + | | Daily |
- | | speed on small glossaries | + | | Latest |
- | | speed on large glossaries | + | | Random |
- | ^ Themeing | + | | Search glossary |
- | | - search form | + | ^ Content |
- | | - node overview | + | | Input, automatic |
- | | - definition fields | + | | Input, automatic, stop list |
- | | - each feature block | n.a. | Yes | + | | Input, explicit |
- | | Implementation | + | | Output, automatic |
- | ^ Developer features | + | | auto " |
- | | XML-RPC API | + | | Disambiguation pages | n.a. |
- | | UI module separate from Data API | No | No | | + | | Disambiguation targeting in links | |
+ | ^ 3rd party integration | ||
+ | | [[http:// | ||
+ | | Views: basic | core | core + specific | ||
+ | | Views: default views | No | No | | ||
+ | | [[http:// | ||
+ | | [[http:// | ||
+ | ^ Performance | ||
+ | | memory needs/ | ||
+ | | speed on small glossaries | ||
+ | | speed on large glossaries | ||
+ | ^ Themeing | ||
+ | | - home page | ||
+ | | - search form | ||
+ | | - node overview | ||
+ | | - definition fields | ||
+ | | - each feature block | n.a. | Yes | ||
+ | | Specific class on glossary links | | Yes | ||
+ | | Implementation | ||
+ | ^ Developer features | ||
+ | | XML-RPC API | ||
+ | | Web services security | ||
+ | | UI module separate from Data API | No | No | | ||
- | Obviously, in all cases, a " | ||
- | ", as in all Open Source software. | ||
+ | Obviously, in all cases, a " | ||
+ | ====== Documentation ====== | ||
- | ===== Drupal 4.x to 6: Rationale for G2 specificities | + | * Glossary |
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * G2 | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * Glossify | ||
+ | * [[http:// | ||
- | * Optimization for large glossaries: this is the need expressed by OSInet, which funded development, | ||
- | * Single glossary: multiple glossaries were not necessary to OSInet, which funded development | ||
- | * Explicit linking to terms with dfn elements: | ||
- | * limits system workload | ||
- | * allows invisible marking of entries made of other entries. Think: XML-RPC, points to XML and to RPC with glossary.module and various wiki filters, but can point to ' | ||
- | * allows redactor-level choice of | ||
- | * whether to link to an entry: glossary always links if the term matches, which is not always meaningful (" | ||
- | * where to link to an entry: glossary allows only a predefined set of positions (first, last or all matches) | ||
- | * nodes vs terms: this is the most salient difference. | ||
- | * Using custom nodes (g2_entry in g2.module) allows large definitions, | ||
- | * Using terms (glossary.module) allows definitions to be bound to custom nodes instead of being nodes on their own | ||
- | * Alphabar maintenance: | ||
g2/choosing.1294823859.txt.gz · Last modified: 2020/11/23 17:23 (external edit)