|
|
| (10 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| [[Category:Basic Concepts and Terminology]]
| | {{context|Basic Concepts and Terminology|Manipulation of Visual Elements}} |
| [Context: [[Home|HL Kit]] … [[Basic Concepts and Terminology]] … [[Manipulation of Visual Elements]]]
| |
|
| |
|
| ==Overview== | | ==Overview== |
| Line 10: |
Line 9: |
| The topics below explain the most important differences that you need to be aware of. | | The topics below explain the most important differences that you need to be aware of. |
|
| |
|
| *{{fl|x}} | | *{{fl|Controlling Table Contents}} |
| *{{fl|x}} | | *{{fl|Tables Use Templates}} |
| *{{fl|x}} | | *{{fl|Sequencing Through Sort Sets}} |
| *{{fl|x}} | | *{{fl|Adding Items to Tables}} |
| *{{fl|x}} | | *{{fl|Using Choosers}} |
| *{{fl|x}} | | *{{fl|Controlling Table Rows and Columns}} |
| *{{fl|x}} | | *{{fl|Template Sizing Within Tables}} |
| *{{fl|x}} | | *{{fl|Table Headers and Footers}} |
| *{{fl|x}} | | *{{fl|Tables Always Auto-Size}} |
| *{{fl|x}} | | *{{fl|Keying on Items Within Tables}} |
| | |
| ==Controlling the Contents==
| |
| | |
| The purpose of tables is to display a collection of picks or things that are related in some way. For example, all the attributes for a character are shown in a table, all the skills are shown in a table, all the weapons and armor are broken up across multiple tables, etc. So the first order of business with a table is identifying the set of picks or things to be viewed.
| |
| | |
| Tables are generally associated with a specific component. This component establishes the first criteria for determining which objects are displayed in the table. If an object derives from the specified component, then it is valid for inclusion in the table. In many situations, this is all that's required.
| |
| | |
| However, there are times when additional filtering is required. In this case, you can specify an additional tag expression that is applied to every object that derives from the component. This is referred to as the "List" tag expression, since it identifies which objects are shown within the list of objects for the table. Any object that satisfies the List tag expression are included in the table, while any object that does not is omitted.
| |
| | |
| ==Tables Use Templates==
| |
| | |
| template for showing
| |
| template for choosing
| |
| | |
| ==Sequencing Through Sort Sets==
| |
| | |
| | |
| ==Adding Items==
| |
| | |
| actually two separate tables - one for display and one for selection
| |
| candidate tagexpr
| |
| add template
| |
| add item script
| |
| titlebar script
| |
| description script
| |
| | |
| ==Headers and Footers==
| |
| | |
| header title script
| |
| header template
| |
| footer template
| |
| | |
| ==Tables Always Auto-Size==
| |
| | |
| | |
| ==Controlling Rows and Columns==
| |
| | |
| columns attribute
| |
| maxrows and maxcolumns via scripts
| |
| | |
| ==Keying on Items==
| |
| | |
| itemcount
| |
| itemsshown
| |
Context: HL Kit … Basic Concepts and Terminology … Manipulation of Visual Elements
Overview
Table portals behave in significantly different ways from other types of portals. Since you will be using tables extensively in your data files, it's critical that you become familiar with the nuances of working with tables.
Topics
The topics below explain the most important differences that you need to be aware of.
