Lexmark X925 Lexmark Document Distributor - Page 19

Evaluating code quality with JSLint

To check for problems in your script code during builds, you can enable the included version of JSLint. JSLint evaluates

code for overall quality, including syntax, structure, and style conventions, which may help avoid runtime errors by

finding issues that cause compiler errors.

For more information about the specific checks carried out by JSLint, see the JSLint instructions at

www.jslint.com

.

Note that some checks specific to the use of JavaScript with HTML are omitted from LDD. Additionally, a different

comment, described in the following, is used to identify functions defined later in or outside of the script and LDD

objects as global variables.

When JSLint is enabled, code is parsed during project builds. Any warnings generated are shown in the Problems view.

Note:

If the Problems view does not appear in Eclipse, then see the documentation for Eclipse.

To enable JSLint during the build:

1

In Eclipse, click

Window

>

Preferences

.

2

In the category list, expand

Lexmark

, and then select

JSLint

.

3

Select

Enable JSLint

.

4

If necessary, configure the checks to be carried out by JSLint, and then click

OK

.

Note:

Project builds for large solutions may be noticeably slower when JSLint is enabled. You may want to enable

JSLint only while debugging.

Avoiding warnings for functions and LDD objects

To identify LDD objects and indicate functions defined later in or outside of the script to JSLint, use the

comment

/**jsLint

variableName

*/

.

For example, to identify the LDD top

‑

level objects, include this comment in the script:

/**jsLint caller,confirm,confirmTarget,context,credentials,printerIP,taskInfo */

Understanding types of scripts

Using profile scripts

Most workflow solution projects include at least one profile script, which, after being assigned to a profile using the

Device Policy Editor, can be executed from a printer or software client. A profile script may have any file name other

than the names reserved for auto

‑

configure scripts, and each profile script file should contain a

main()

function.

All LDD objects are available for use in profile scripts, and profile scripts can access library scripts.

The script file TestMFP.js in the TestMFP example template is an example of a profile script.

Using library scripts

Library scripts, which can be accessed only by other scripts, can be used to contain common functionality, such as

functions for database access, logging, and progress monitoring. Each function in a library script should use objects and

methods appropriate only for scripts that will call it. For example, a library script called by a scheduled script should

not use prompt objects or any scan methods.

Developing workflow solutions

19

Section	Page
Contents	2
Getting started	5
Prerequisite skills for developing workflow solutions	5
Prerequisite skills for developing LDD system components	5
Understanding workflow solutions	6
Understanding solution types	7
Version compatibility of workflow solutions	8
Understanding components	8
What is the LDD SDK?	8
Minimum system requirements	8
Supported printers	9
Supported ECM platforms	12
Getting support	12
Preparing for development	13
Installing the development environment	13
Manually associating JavaScript files with Eclipse	14
Accessing the Lexmark Document Distributor Script Reference Guide	14
Developing workflow solutions	15
Best practices for solution design	15
Creating a new workflow solution project	16
Understanding the contents of a workflow solution project	16
Managing solution projects	17
Editing the properties of an existing workflow solution project	18
Referencing a workflow solution project	18
Evaluating code quality with JSLint	19
Understanding types of scripts	19
Using profile scripts	19
Using library scripts	19
Adding a library script to a solution	20
Accessing the functions of a library script	20
Using auto-configure scripts	20
Using auto-configure methods	21
Configuring the home screen with auto-configure	21
Using forms merge scripts	29
Scripting for different stages of a forms merge	29
Using the PrintClass service with forms merge scripts	32
Printing forms on printers with forms cards	32
Using scheduled scripts	32
Understanding the objects used in solution development	33
Top-level objects	33
Prompts	33
Services	34
Configuring solutions	35
Managing solution settings	35
Managing device policies	37
Managing the Solution Status Page	41
Managing formsets	42
Managing custom reports	42
Using the included document processing components	43
Bar code read support	43
Bar code write support	45
OCR support	46
Using the included solution database	48
Services	49
Understanding the Job Submission Web Service	49
Understanding dynamic prompting support	50
Using Kerberos authentication	51
Developing workflow solutions for previous versions of LDD	51
Testing and deploying workflow solutions	52
Testing with the MFP emulator and performance simulator	52
Accessing the MFP emulator or performance simulator	52
Using the interactive MFP emulator	52
Using the interactive MFP emulator with an LDD system	52
Simulating a scan task	53
Saving print jobs	53
Using the performance simulator	53
Preparing and running tests in the performance simulator	53
Configuring advanced properties	54
Supplying answers to prompts	61
Using JConsole to monitor and modify a running test	63
Determining the single-server throughput for a solution	65
Deploying a solution directly to an LDD server system	66
Restarting the Lexmark Solutions Application Server	67
Distributing a solution file and installing the solution using LMC	67
Managing the LDD 4.x System List	67
Building a workflow solution from the command line	68
Developing components	70
Understanding component design	70
Best practices for component design	70
Creating a new component project	71
Understanding the contents of a component project	71
Including a component in a workflow solution project	72
Troubleshooting	73
Network connection problems occur when installing or updating plug-ins in Eclipse	73
The Lexmark Solution Development perspective or other features are missing	73
Auto-complete does not work or items are missing in auto-complete lists for LDD objects	73
A properties file updated using revision control does not update	74
LDD system times out when directly exporting a solution	74
The MFP emulator does not run	74
The MFP emulator runs but cannot be discovered in LMC	75
The Backspace and left arrow keys do not work when viewing LMC in Eclipse	75
Notices	76
Edition notice	76
Trademarks	76
UNITED STATES GOVERNMENT RIGHTS	76
The Apache Software License, Version 1.1	77
Apache License Version 2.0, January 2004	77

Lexmark X925 Lexmark Document Distributor - Page 19

Evaluating code quality with JSLint, Understanding types of scripts, Using profile scripts

Page 19 highlights