Glossary of Tags F - R

^ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z ? Panel

Select the first letter of the word from the list above to link to appropriate section of the glossary.

F

face: Within a file, *.tag, defines the face which can be place on a tame button. Unlike an image this tag includes both an image and a text face. Depending on the use of the *TAGNAME* either the image or the test will appear on the tame page.

<tame>
face: *TAGNAME* BUTTON-FACE-TEXT DOCUMENT-LOCATION HTML-OPTION-LIST
</tame>

TAGNAME:

The name to use as the tag name for the image.

HTML-OPTION-LIST:

List of options for the image. Can include any valid options for the HTML <image> tag.

Example:

<tame face: *buy* buy buy.gif alt="[ Buy ]" width=82 height=28 border=0>

Adding this command to *.tag file will provide a "buy button" that can be used on a tame page by using the syntax {*buy*}.

foreach: Iterates through all the rows in the table. foreach will generate a HTML/TAME area for each row of the table designated by the workwith command. This tag established a context of a particular row, therefore the row indicator in the data retrieval tags can be omitted.
<tame foreach:: HTML-AREA>: Note the double colons.

HTML-AREA:

The HTML to format the data and the TAME command to retrieve the required information from a table.

Note: foreach must be used with the workwith command.

Example:

<table width=50% cellpadding=1 border=2>
<tr><td>ITEM</td> <td>PRICE</td> <td>DESCRIPTION</td> <td>SELECT TO PURCHASE</td></tr>
<tame workwith: data>
<tame foreach::
<tr><td>{?item}</td>
<td>{?price}</td>
<td>{?descrip}</td>
<td><tame ^buy: {?item}></td></tr>
>
<tame /workwith>
</table>

This example will provide the item, price, description and a buy button for each item in the table data. The information will be presented on the page within a HTML table.

field-name: The column name of a field in a database. The field is distingished by a ? at the beginning of the name.

{?FIELD-NAME}

Example:

<tame form>
<tame workwith: product.tdb>
ITEM NUMBER: {?item} 
PRICE: {?item,price} 
DESCRIPTION: {?item,descrip} 
<tame /workwith>
<tame /form>

This example presents an item with price and description to the customer.

G

getcart: Accesses variables saved in the cart for presentation.
<tame getcart: VARIABLE >

H

hidden: An input type that allows for information store with a page to be hidden from view.

Example:

<tame hidden: computer.item computer>
<tame hidden: computer.qty 1>
<tame buysubmit: Go to order page>

Using the hidden input type, the computer item code and quantity values are associated with the page, but are not visible to the customer. The buysubmit will add the computer to the shopping cart.

I

image

Defines a tame image that can be placed in documents as a single tag or used within other tame commands.

<tame>

image: *TAGNAME* DOCUMENT-LOCATION HTML-OPTION-LIST

</tame>

TAGNAME:: The name to use as the tag name for the image.

HTML-OPTION-LIST:: List of options for the image. Can include any valid options for the HTML <image> tag.

Example:

<tame image: *ball* /images/ball.gif alt="*" width=14 height=14 align=bottom>

See also: place, ^goto, define, face, creating tags

include: Associates the user-defined commands within a tag file with the *.tam file. The include must be presented prior to using functions define in the tag file.

<tame>include: PATH-FILE</tame>

Example:

In the file coolfile.tam:

<tame>include: coolfile.tag </tame>

All the information and variables defined in the coolfile.tag are now accessable in the coolfile.tam file.

See Also: define, place, face, Creating your own tags

input_quality

input_quality2

input_qty

ITEM: Item code corresponding to an item entry in the product database. When the ITEM is already being supplied by another input box or hidden variable on the page, leave off the arguments or make the ITEM argument null by using an empty pair of square brackets [ ].

item_image: ??

HTML-ARGUMENT-AREA1

Text or image to display if the item-code is not in the cart.

HTML-ARGUMENT-AREA2

Text or image to display if the item-code is in the cart.

Note: This feature is not sensitive to item qualities. It detects only the existence of the item code in the cart. It does not differentiate between items with different qualities such as "color", "size", etc. A red shoe1 in the cart will be the same as a green shoe1 in the cart.

Example

J K L

M

N

new_query: Modifier used with ^link tag to reset a query page to which you return your customer to the first hit. If you don't use this modifier, the query sequence available to the customer the last time he was on the page will be used. Therefore, your customer will not necessarily start out on hit 1.; Note: When you use pass on a link, you don't need new_query.

<tame> new_query ^LINK/^GOTO: DOCUMENT-LOCATION HTML-ARGUMENT-AREA </tame>

Example:

Using the new_query modifier will return the customer to the first record returned by the query. This is useful if an item has been selected and you want the customer to have access to an entire listing for his next choice.

See Also: query.pan, subquery.pan, Data Access

O

Outside: ^link modifier. Creates a link outside of tamespace to another domain or a pure html page. When a customer passes through an ouside link, tame will loose the lock on the customer's identity. Pure html pages can be displayed using outside links as long as the customer is requried to use the browser back button to continue browsing. A link from a html page will ot contain tame tracking information such as the shopping cart.

P

page_end: This tag is place a the end of a tame page to provide a footer on the page. The information presented is defined in the shop admin wizard under the page_end sections for application and catalog pages. You can also create unique page_end information by using the define tag at the top of a page.

Note: The page_end tag is used in conjunction with the html </body> and </html> tags.

Example:

<html>
<head>
<tame tamehead: index.tam page>
<title>Books and Video Shop Front Page</title>
</head>
<body bgcolor="ffffff" text="000000" link="0000ff" vlink="0000ff" alink="0000ff">
You would put your information here [html and tame code]
<tame page_end>
</body>
</html>

This is a standard tame page which will present the page_end define in the admin wizard on the bottom of the page.

<html>
<tame> define page_end: Special orders are gladly accepted. </tame>
<head>
<tame tamehead: index.tam page>
<title>Books and Video Shop Front Page</title>
</head>
<body bgcolor="ffffff" text="000000" link="0000ff" vlink="0000ff" alink="0000ff">
You would put your information here [html and tame code]
<tame page_end>
</body>
</html>

This is a standard tame page which will present the unique page_end "Special orders are gladly accepted." at the bottom of the page instead of the page_end defined in the admin wizard.

Q

quality_price: This modifier of quality tags is used to associate a price with a quality of an item. Therefore, the additional cost is only added to the base item price, if the quality is select. This modifier must end with a semicolon (;) before the tag name.

Note: This modifier can be used with radio_quality, box_quality, select_quality and text_quality.

Note: The radio_quality and box_quality tags include the pricelet as an optional argument to provide the quality_price. See radio_quality and box_quality for this syntax.

<tame> quality_price: CLASS QUALITY VALUE PRICELET; QUALITY-TAG </tame>

Note: With the radio_quality and box_quality tags a shortened version of this tag can be used:
<tame> quality_price: PRICELET; QUALITY-TAG </tame>

PRICELET:

The skew code to add to the item's base price when the quality is selected.

QUALITY-TAG:

The appropriate syntax for radio_quality, box_quality, select_quality or text_quality.

Example:

<tame form>
A Personalized Widget which costs {?widget,price}
<tame> quality_price: widget size large 10; quality_price: widget size medium 5; select_quality: widget size small medium large</tame>
<tame> ^buy: widget Buy a Widget</tame>
<tame /form>

In this example, a customer will see a drop-down selection list of sizes for the widget. If he selects small or medium the base item price will be used. However, if he selects the medium size a $5 additional price will be added to the widget's base price or $10 if he selects large.

<tame form>
<tame> quality_price: 5; box_quality: dress with belt</tame> With matching belt for an additional $5 
<tame> quality_price: 10; box_quality: dress size xlarge</tame> Make it extra large for an additional $10 
<tame> box_quality: dress color yellow</tame> YELLOW instead of the standard white for no additional charge 
<tame> ^buy: dress</tame> 
<tame /form>

In this example, the shortened version of the quality_price modifier is used with the box_quality. The customer can select three special options associated with the item "dress". Based on the boxes checked the customer can customize the "dress" with a matching belt for $5, extra large size for $10 or the color yellow which has no additional cost.

quality_skew: This modifier of quality tags is used to associate a skew code with a quality of an item. Therefore, the additional skew information is only added to the base item price, if the quality is select. This modifier must end with a semicolon (;) before the tag name.

Note: This modifier can be used with radio_quality, box_quality, select_quality and text_quality.

Note: The radio_quality and box_quality tags include the codelet as an optional argument to provide the quality_skew. See radio_quality and box_quality for this syntax.

<tame> quality_skew: CLASS QUALITY VALUE CODELET; QUALITY-TAG </tame>

Note: With the radio_quality and box_quality tags a shortened version of this tag can be used:
<tame> quality_skew: CODELET; QUALITY-TAG </tame>

CODELET:

The skew code to add to the item code when the quality is selected.

QUALITY-TAG:

The appropriate syntax for radio_quality, box_quality, select_quality or text_quality.

Example:

<tame form>
A Personalized Widget which costs {?widget,price}
<tame> quality_skew: widget size small 1; quality_skew: widget size medium 2; quality_skew: widget size large 3; select_quality: widget size small medium large</tame>
<tame> ^buy: widget Buy a Widget</tame>
<tame /form>

In this example, a customer will see a drop-down selection list of sizes for the widget. Based on the size he selected a 1, 2 or 3 will be added to the widget's item code to present an extended item code. This code assist with order fulfillment.

<tame form>
This is an dress which costs {?1000,price}
<tame> quality_skew: 1432; box_quality: example with belt</tame> With matching belt for an additional $5 
<tame> quality_skew: 345; quality_price: 10; box_quality: example xlarge</tame> Make it extra large for 10 
<tame> quality_skew: 179; box_quality: example color yellow</tame> YELLOW instead of the standard white 
<tame> ^buy: example</tame> 
<tame /form>

In this example, the shortened version of the quality_skew modifier is used with the box_quality. The customer can select three special options associated with the item "dress". Based on the boxes checked the customer can customize the "dress" with a matching belt, extra large size or the color yellow. Each quality will append the item code with the skew number provided by the quality_skew. If the customer selects a belt and yellow the item number on the invoice will read 10001432179.

query.pan: To place a panel on the customer's screen which asks for an entry of keywords and provides a button with which to submit the search and a button to page through the results.
<show_panel: query.pan OPTION . . .>

Note: Must be used inside a workwith area.

OPTIONs

Where OPTIONs are selected from the following:

BORDER [SIZE]

The border size around the panel. The default is set in the administration shop.

QUERYVAR [NAME]

The name of the variable that contains the search query. Defaults to "query".

PRIORFACE [BUTTON-FACE-AREA]

Text or tame image for the prior button face. Defaults to "Prior".

Note: The "prior" button is never available with wgrep database access. This is an SQL only button. For wgrep, use the ^submit button to start the search over at the beginning.

NEXTFACE [BUTTON-FACE-AREA]

Text or tame image for the next button face. Defaults to "Next".

SUBMITFACE [BUTTON-FACE-AREA]

Text or tame image for the new query button face. Defaults to "New Query".

SUBMIT_PAGE [PAGE]

Page to submit a new search to. Default is to loop on the same page.

NOSEARCH

Hides the next query button.

Example

<tame>
show_panel: query.pan BORDER 5 SUBMITFACE [New Search] NEXTFACE [Next HITS]
</tame>

might present the following panel:

R

radio: Creates a HTML radio button element. Can prefill value automatically.
<tame radio: VARIABLE VALUE>

VALUE:

Optional value for the button. When not given, value is taken from the assigned variable.

Example:

<tame checked radio: color red> Red
<tame radio: color green> Green
<tame radio: color blue> Blue

In this example three radio buttons will appear with the text Red, Green or Blue next to each one. The red button will be checked as the default.

Modifier: checked

item	price	description	detail
P001	4.95	"Hot item"	hotpage.tam

Password:

User name:
Password: