Optimizing performance for imagesImages require additional processing
time when the form is rendered. If you choose to use images, use
compact file formats and the smallest possible image dimensions
to minimize the file size. Size the images to the intended dimensions before
adding them to the form. Avoid resizing images after adding them
to the form.
Ensure that corners are square and lines are exactly horizontal
and vertical to optimize performance when the form is rendered.
Lines that appear to be exactly vertical or horizontal may have
a slight slope.
You can check the slope of horizontal and vertical lines in the
Layout palette. The Height option represents the slope of a horizontal
line and the Width option represents the slope of a vertical line.
In the following example, a vertical line has a small slope of approximately
0.5 millimeters. A width of 0mm makes the line exactly vertical.
Optimizing performance for discrete option choicesSeveral
objects provide discrete option choices: check boxes, list boxes,
and radio buttons. List boxes and check boxes are rendered more
quickly than radio buttons.
Optimizing performance for subformsDesigner distinguishes boilerplate
or static objects, such as text, lines, and images, from objects
that contain variable content, such as text fields and image fields.
For example, interactive forms can include text labels that provide
information to the user and text field objects that capture information
from the user.
A subform is a type of object that contains content. Subforms
are often grouped based on the structure of the data that is bound
to each subform. The ability to bind repeating, optional, and conditional
data groups to subforms reduces the risk of design errors that may
occur if you use scripts to achieve the same results.
For example,
you can create a subform that includes objects for repeating data
groups. When rendering the form, Forms creates as many instances
of the subform as necessary to represent all the data groups.
When using subforms, keep the following in mind for optimal performance:
Repeating and nested subforms require additional processing
to render the form. Avoid using them unless they offer better performance
than alternative options. For example, a repeating subform may eliminate
the need for a number of repeating objects.
Allowing
page breaks in subforms causes additional processing, even if Forms does
not apply page breaks. For example, the location, size, or content
of a subform may prevent a page break. To optimize performance,
turn off page breaks in subforms. By default, page breaks are allowed.
Optimizing performance for text fieldsBy default, entries in
text field objects are formatted as plain text. You can change this
option to allow rich text formatting.
However, for plain text entries, the font, style, and size used
at design time are applied to user input. The form can be rendered
more efficiently by using the text properties used in the form design.
For rich text entries, users can customize the font style and
size for text entered in the object. Although rich text entries
may be useful in some situations, such as for narrative information,
the extra attributes decrease performance.
Performance of objects on master pages versus pagesObjects
on master pages require additional processing time when Forms renders
the form. If possible, place objects on pages.
Tips for reducing the number of objectsThe
file size of a form is affected by the number of objects on the
form. Consider these general tips to minimize the number of objects
on forms:
When creating a box, use a single rectangle object instead
of joining four individual lines.
When creating a border for a field or subform object, use
the object’s border attributes instead of creating a separate box.
When creating backgrounds for objects, use a background fill
instead of creating a separate shaded box object.
For captions, use an object’s caption property instead of
using a separate text object.
Combine multiple text objects into a single text object.
This strategy is particularly useful after importing forms into
Designer.
Tips for reducing the complexity of objectsThe
file size of a form is affected by the complexity of the objects
on the form. Simple objects can be processed more efficiently than
complex objects. Consider these general tips to minimize the complexity
of objects:
Keep the number of fonts, styles, and sizes to a minimum
to take advantage of cached font information.
Use fixed objects instead of dynamic objects that shrink
and grow, if possible.
Avoid building objects on top of each other, especially more
than three layers deep.
|
|
|