|
|
Line 7: |
Line 7: |
| <nowiki>{{Key Start| id = Example | title = Example key | description = Only a demo }}</nowiki> | | <nowiki>{{Key Start| id = Example | title = Example key | description = Only a demo }}</nowiki> |
| <nowiki>{{Lead | 1 | Blätter gegenständig | 2 }}</nowiki> | | <nowiki>{{Lead | 1 | Blätter gegenständig | 2 }}</nowiki> |
− | <nowiki>{{Lead | 1 | Blätter wechselständig | 18</nowiki> | + | <nowiki>{{Lead | 1 | Blätter wechselständig | 18 </nowiki> |
| <nowiki> |image=[[Image:xyz.jpg|thumb|200px|A caption for the image]] }}</nowiki> | | <nowiki> |image=[[Image:xyz.jpg|thumb|200px|A caption for the image]] }}</nowiki> |
| <nowiki> ... any number of leads ...</nowiki> | | <nowiki> ... any number of leads ...</nowiki> |
Line 130: |
Line 130: |
| ===Known problems=== | | ===Known problems=== |
| | | |
− | # A plain three column layout is less than satisfactory; the occasional wide taxon names force the whole last column to be very wide.
| |
− | #* To some extent, this is already worked around by providing a four-column layout with alternating colspan (33% of table width is assigned to statement, if no taxon is present, or to taxon, if that is present. However, this still means that the statement may be presented shorter than necessary.
| |
− | # Clicking on the hyperlinks usually has no effect if the screen already contains the target lead.
| |
− | #* Proposed solution: some javascript additions. Note: JS can not be called directly from within the wiki text for security reasons, or any user could reprogram the wiki into a dangerous tool.
| |
| # Leads do not automatically renumber. | | # Leads do not automatically renumber. |
| #* There is an obvious service solutions for this: The project would have to program a "bot" program, the works through all keys that have a category like "Please renumber" set, renumbering the key in an optimal way, and then deleting (or commenting out) the category. | | #* There is an obvious service solutions for this: The project would have to program a "bot" program, the works through all keys that have a category like "Please renumber" set, renumbering the key in an optimal way, and then deleting (or commenting out) the category. |
− | # There are no lead dots running from the statement to the number.
| |
− | #* Attempting to fix this with <nowiki><span style="float:right"> . . . .</span></nowiki> did not work well!
| |
− | #* Can this be fixed with a repeated background image and non-transparent text? Could be worth testing!
| |
| | | |
| | | |
Line 144: |
Line 137: |
| | | |
| * Styles in [[MediaWiki:Common.css]], one of which refers to a background image which must be available, and it needs the StringFunctions extension installed. | | * Styles in [[MediaWiki:Common.css]], one of which refers to a background image which must be available, and it needs the StringFunctions extension installed. |
− | * The target highlighting depends on code in [[MediaWiki:Common.js]] | + | * The internal link target highlighting depends on code in [[MediaWiki:Common.js]] |
− | * The associated templates are: [[Template:Lead]], and [[Template:LeadQuestion]] | + | * The associated templates are: [[Template:Key End]], [[Template:Lead]], and [[Template:LeadQuestion]] |
− | * Documentation templates at: [[Template:SingleAccessKey/doc]], [[Template:Lead/doc]] | + | * Documentation templates at: [[Template:Key Start/doc]], [[Template:Key End/doc]], [[Template:Lead/doc]] |
| * Secondary tool templates are [[Template:Trim]], [[Template:Documentation]], [[Template:Documentation/subpage]], [[Template:Documentation/docname]], [[Template:Documentation/preload]]. | | * Secondary tool templates are [[Template:Trim]], [[Template:Documentation]], [[Template:Documentation/subpage]], [[Template:Documentation/docname]], [[Template:Documentation/preload]]. |
| | | |
This is a documentation subpage for Template:Key Start (see that page for the template itself).
It contains usage information, categories and other content that is not part of the original template page.
The key is a table with a dummy column to enable partial overlap between left and right text in different rows. Overlap is possible only between a long lead statement with a short number pointer, long lead statements with a long taxon name can not overlap. Each lead is a separate row, if images are present they are added in an additional row where required.
Javascript programmability: Each row contains an id attribute with "L" + lead number + "row", the lead cell itself an id attribute with "L" + lead number. The table is styled mostly using css classes, with the text span background an exception (to allow parameterization of the background).