g2:choosing
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
g2:choosing [2011/01/12 09:16] – [Choosing a glossary-type module] expanded for DDD code sprint fgm | g2:choosing [2011/01/22 22:08] – G2 D7 now available fgm | ||
---|---|---|---|
Line 1: | Line 1: | ||
Back to [[g2: | Back to [[g2: | ||
+ | ====== Choosing a glossary-type module ====== | ||
+ | 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 " | ||
- | + | ^ Feature | |
- | ====== Choosing a glossary-type module ====== | + | ^ Drupal-related |
- | + | | Drupal 7.x | No | | |
- | 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, | + | | Drupal 6.x | Yes |
- | + | | Drupal 5.x | Yes | |
- | ^ Feature | + | | Drupal 4.7.x | Yes |
- | ^ Drupal-related | + | | Drupal 4.6.x | Yes |
- | | Drupal 7.x | No | | + | | Earlier Drupal versions |
- | | Drupal 6.x | Yes | + | | AJAX | No | Some autocompletion |
- | | Drupal 5.x | Yes | + | | Storage |
- | | Drupal 4.7.x | Yes | + | | Revision support |
- | | Drupal 4.6.x | Yes | + | | Simpletest |
- | | AJAX | No | Some autocompletion | + | ^ Services provided |
- | | Storage | + | | multiple glossaries on one site |
- | ^ Services provided | + | | RSS feeds on entries |
- | | multiple glossaries on one site | + | | RSS feeds on additional vocabularies | No |
- | | RSS feeds on entries | + | | classify entries |
- | | RSS feeds on additional vocabularies | No | + | | commenting on entries |
- | | classify entries | + | | private editorial information |
- | | commenting on entries | + | | alphabar maintenance |
- | | private editorial information | + | | remote glossaries |
- | | alphabar maintenance | + | | steganographic content protection | | No | |
- | | content filtering, automatic | + | | RDF information |
- | | content filtering, explicit | + | ^ i18n ^ ^ ^ |
- | | feature blocks | + | | Translation template supplied |
- | | remote glossaries | + | | Multilingual blocks |
- | | Security | + | | Translatable |
- | ^ 3rd party integration | + | ^ Feature blocks |
- | | [[http:// | + | | Alphabar |
- | | Views: basic | core | core + specific | + | | Daily |
- | | Views: default views | No | No | | | + | | Latest |
- | | [[http:// | + | | Random |
- | | [[http:// | + | | Search glossary |
- | ^ Performance | + | ^ Content |
- | | memory needs/ | + | | Input, automatic |
- | | speed on small glossaries | + | | Input, automatic, stop list |
- | | speed on large glossaries | + | | Input, explicit |
- | ^ Themeing | + | | Output, automatic |
- | | - search form | + | | auto " |
- | | - node overview | + | | Disambiguation pages | n.a. |
- | | - definition fields | + | | Disambiguation targeting in links | |
- | | - each feature block | n.a. | Yes | + | ^ 3rd party integration |
- | | Implementation | + | | [[http:// |
- | ^ Developer features | + | | Views: basic | core | core + specific |
- | | XML-RPC API | + | | Views: default views | No | No | |
- | | UI module separate from Data API | 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 | | ||
Line 56: | Line 77: | ||
", as in all Open Source software. | ", as in all Open Source software. | ||
+ | ====== Documentation ====== | ||
- | + | * Glossary | |
- | ===== Rationale for G2 specificities | + | * [[http:// |
- | + | * [[http:// | |
- | + | * G2 | |
- | + | * [[http://cvs.drupal.org/viewvc.py/ | |
- | | + | * [[http://wiki.audean.com/ |
- | + | * Glossify | |
- | | + | * [[http:// |
- | + | ||
- | * 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.txt · Last modified: 2023/05/27 16:05 by fgm