User Tools

Site Tools


g2:choosing_next

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
g2:choosing_next [2008/10/30 14:04] – More info for glossify where CCK and views could be used. eafarrisg2:choosing_next [2011/01/12 13:45] – [G2 advocacy] merged content from "choosing" page fgm
Line 566: Line 566:
       </ul>       </ul>
     </li>     </li>
 +  <li>Single glossary: multiple glossaries were not necessary to OSInet, which funded development</li>
 +  <li>Optimization for large glossaries: this is the need expressed by OSInet, which funded development, to support its 5000+ term glossary of computing, for which glossary.module, even when coupled with flexinode or early CCK to bind blob content to terms, was not really efficient enough</li>
 +  <li>Using custom node type (g2_entry in g2.module) allows large definitions, with the complete drupal feature set for nodes. At the time of Drupal 4.7, neither flexinode not CCK were a reasonable choice for a generic module</li>
 +  <li>Manual alphabar maintenance: large glossaries will most of the time use all available initials, so the processing cost of maintaining it is not justifiable</li>
   </ul>   </ul>
- 
 </html> </html>
- 
  
 ====== Glossary advocacy ====== ====== Glossary advocacy ======
Line 604: Line 606:
 </html> </html>
  
-===== Glossify advocacy =====+ 
 +====== Glossify advocacy ======
 <html> <html>
  
g2/choosing_next.txt · Last modified: 2023/05/27 15:24 by fgm