7.1
Table Of Contents
- Table of Content
- Overview
- Understanding PrintShop Mail Web
- Getting Started
- The PrintShop Mail Web Interface
- Publishing Workflow
- Ordering Workflow
- New Document
- Order Manager
- Checkout
- Companies
- Users
- Publication Types
- Collections
- Settings
- About
- License
- Roles
- Languages
- Web Design
- Maintenance
- Settings
- Currencies
- Tax Rates
- Shipping Rates
- Calendar
- Production Settings
- User Input Field Defaults
- Output Folders
- Job options
- Printers
- E-mail Settings
- E-mail Addressees
- Managing E-mail Templates
- Modules Settings
- Enabling a MIS connector
- Installed modules
- Properties
- Enabling a Print Production connector
- Installed modules
- Properties
- Requirements
- Configuring the module
- The PayPal Sandbox
- Processing orders
- Requirements
- Configuring the Authorize.net module
- Test mode
- AVS and CCV checks
- Payment page
- Requirements
- Requesting a test account
- Configuring the iDEAL test dashboard
- Configuring the iDeal module
- Requirements
- Configuring the Moneris module
- Test mode
- Requesting a live account
- AVS and CVD checks
- Payment page
- Add a new Module
- Configure a module
- Delete a Module
- XML (eXtensible Markup Language)
- Options
- Sample POST receive script
- Interaction With PrintShop Mail Design
- Introduction to Regular Expressions
- Introduction
- Skinning Guide
- Getting started
- Creating your own skin
- The template file
- HMTL Outline
- Styling
- Key Concepts
- Style organization
- Header
- User information
- Menu bar
- Background
- Overview tables
- Edit forms
- Sub menus
- Special variables
- Variables for template files
- Variables for style files
- Creating page exceptions
- Creating a page specific template file
- Modifying a page specific template file
- DOM manipulation using jQuery
- Launching code on Document Ready
- Populating fields with computed values
- Removing elements from the DOM
- Adding information to the DOM
- Customizing the store front
- Storefront class
- Creating a hierarchical tree
- Adding a live search option
- Copyright Information
- Index
<legend id="cGeneralLegend">
<span id="cGeneralLegendLabel">General</span>
</legend>
<div>
<div id="fcUserNameLine">
<span id="fcUserNameLabel">
User name:<span>*</span>
</span>
<span>
<input type="text" value="pp" name="fcUserName"
id="fcUserNameField"/>
</span>
</div>
<div id="fcPersonCodeLine">
<span id="fcPersonCodeLabel">Person code:</span>
<span>
<input type="text" value="" name="fcPersonCode"
id="fcPersonCodeField"/>
</span>
</div>
</div>
</fieldset>
</div>
</form>
</div>
The <form> tag is used to process the information entered by the user. The contents of the <form> tag are captured by a
<div> with a unique id.
Form head
The first content element is the form header. In the default skin the information in this tag is used to visually group the ele-
ments in the form.
.formHeader {
display: block;
width: 100%;
background-color: <? generateSkinMainColor(); ?>;
color: #FFFFFF;
padding: 2px;
font-weight: bold;
}
Form lines
Each line in an edit form is enclosed by a <div> tag. This element has an unique id and a Formline class. Normally each line
contains two child elements: a label and a field. The form fields can be of various types, for example: plain text input, a pull
©2010 Objectif Lune Inc - 236 -