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 revision Previous revision
Next revision
Previous revision
g2:choosing_next [2008/10/30 14:51]
eafarris Added the glossify module to the comparison.
g2:choosing_next [2011/01/12 14:47] (current)
fgm
Line 1: Line 1:
 ====== Warning ====== ====== Warning ======
  
-This is a work-in-progress page for NancyDru, fgm and eafarris, to update http://​drupal.org/​node/​266511 ​and will be updated there once finished. In the meantimeplease refer to http://​drupal.org/​node/​266511 ​instead. +This is a 2008 work-in-progress page for NancyDru, fgm and eafarris, to update http://​drupal.org/​node/​266511 ​but never completed at the time. In 2011update [[g2/choosing|Choosing a glossary module]] ​instead.
  
 ====== Features checklist ====== ====== Features checklist ======
Line 167: Line 166:
     <​td><​img src="​http://​drupal.org/​misc/​watchdog-ok.png"​ alt="​Yes"​ /></​td>​     <​td><​img src="​http://​drupal.org/​misc/​watchdog-ok.png"​ alt="​Yes"​ /></​td>​
     <​td>&​nbsp;</​td>​     <​td>&​nbsp;</​td>​
-    <​td><​img src="​http://​drupal.org/​misc/​watchdog-ok.png" alt="Yes" /></​td>​+    <​td><​img src="​http://​drupal.org/​misc/​watchdog-error.png" alt="No" /></​td>​
     <​td>​CCK</​td>​     <​td>​CCK</​td>​
     </tr>     </tr>
Line 178: Line 177:
     <​td>&​nbsp;</​td>​     <​td>&​nbsp;</​td>​
     <​td><​img src="​http://​drupal.org/​misc/​watchdog-error.png"​ alt="​No"​ /></​td>​     <​td><​img src="​http://​drupal.org/​misc/​watchdog-error.png"​ alt="​No"​ /></​td>​
-    <td>&nbsp;</td>+    <td>Views</td>
     </tr>     </tr>
   <tr>   <tr>
Line 187: Line 186:
     <​td>&​nbsp;</​td>​     <​td>&​nbsp;</​td>​
     <​td><​img src="​http://​drupal.org/​misc/​watchdog-error.png"​ alt="​No"​ /></​td>​     <​td><​img src="​http://​drupal.org/​misc/​watchdog-error.png"​ alt="​No"​ /></​td>​
-    <td>&nbsp;</td>+    <td>Views</td>
     </tr>     </tr>
   <tr>   <tr>
Line 196: Line 195:
     <​td>&​nbsp;</​td>​     <​td>&​nbsp;</​td>​
     <​td><​img src="​http://​drupal.org/​misc/​watchdog-error.png"​ alt="​No"​ /></​td>​     <​td><​img src="​http://​drupal.org/​misc/​watchdog-error.png"​ alt="​No"​ /></​td>​
-    <td>&nbsp;</td>+    <td>Views</td>
     </tr>     </tr>
   <tr>   <tr>
Line 205: Line 204:
     <​td>&​nbsp;</​td>​     <​td>&​nbsp;</​td>​
     <​td><​img src="​http://​drupal.org/​misc/​watchdog-error.png"​ alt="​No"​ /></​td>​     <​td><​img src="​http://​drupal.org/​misc/​watchdog-error.png"​ alt="​No"​ /></​td>​
-    <td>&nbsp;</td>+    <td>Views</td>
     </tr>     </tr>
   <tr>   <tr>
Line 223: Line 222:
     <​td>&​nbsp;</​td>​     <​td>&​nbsp;</​td>​
     <​td><​img src="​http://​drupal.org/​misc/​watchdog-error.png"​ alt="​No"​ /></​td>​     <​td><​img src="​http://​drupal.org/​misc/​watchdog-error.png"​ alt="​No"​ /></​td>​
-    <td>&nbsp;</td>+    <td>Views</td>
     </tr>     </tr>
   <tr>   <tr>
Line 566: Line 565:
       </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 601: Line 602:
  
 <​p>​Within the glossary display, each term may be followed by a link that will initiate a search for the term, if the search module is enabled. For those who have the proper permission, there will also be a link to edit the term itself.</​p>​ <​p>​Within the glossary display, each term may be followed by a link that will initiate a search for the term, if the search module is enabled. For those who have the proper permission, there will also be a link to edit the term itself.</​p>​
 +
 <​p>​The type of glossary indicator that is used is specified for each input format, so, for example, "​Filtered HTML" may use a superscript type of indicator, while "Full HTML" may use a hovertip. Additionally,​ each input format also selects which vocabularies are to be used. So one may, again for example, specify that "​Filtered HTML" filter for Bible verses, while "Full HTML" filters for technical terms.</​p>​ <​p>​The type of glossary indicator that is used is specified for each input format, so, for example, "​Filtered HTML" may use a superscript type of indicator, while "Full HTML" may use a hovertip. Additionally,​ each input format also selects which vocabularies are to be used. So one may, again for example, specify that "​Filtered HTML" filter for Bible verses, while "Full HTML" filters for technical terms.</​p>​
 +
 +<​p>​Using terms (glossary.module) allows definitions to be bound to custom nodes instead of being nodes on their own</​p>​
 +
 </​html>​ </​html>​
  
-===== Glossify advocacy =====+ 
 +====== Glossify advocacy ​======
 <​html>​ <​html>​
  
g2/choosing_next.1225374709.txt.gz · Last modified: 2008/10/30 14:51 by eafarris