8.0
Table Of Contents
- Overview
- New and enhanced features
- Getting started
- Functions
- Function overview
- Render types
- Content modifiers
- Render modifiers
- XML modify
- XML deconstruct and construct
- About XML deconstruct/construct
- xml
- construct
- Deconstructing a project
- Constructing a project
- Working with pages and spreads
- Working with layers
- Working with boxes
- Working with pictures
- Working with text
- Working with tables
- Working with Composition Zones
- Using server XSLT
- Working with lists
- Working with anchored boxes
- Working with placeholders
- Working with metadata
- Working with hidden text
- Administrative Request handlers
- The Modifier DTD
- Sample applications
- Contact Quark
- Legal notice
<form id = form1 method="post" enctype="multipart/form-data">
The common code for browsing the text files and the picture files from the client is:
<TD><INPUT id=box1FileTxt value="File on Client"
readOnly style="WIDTH: 180px; HEIGHT: 22px" ></TD>
<TD><input id=box1File type="file"
size="32" maxlength="256" style="WIDTH: 293px;
HEIGHT: 22px"></TD></TR>
When you click the "Render Document" the following takes place.
The action of the form is defined in the HTML by this line of code in the JavaScriptâ„¢ function
Submit_onClick():
document.getElementById("form1").action = url;
The form's method is POST. The user agent conducts an HTTP post transaction using the value of the
action attribute (the URL), and a message is created according to the content type specified by the
enctype attribute.
Working with QuarkXPress Server Manager
using an HTTP POST request
The methodology is identical to using an HTTP POST with QuarkXPress Server (see above), except
that with Manager, you must use UTF-8 as character encoding in forms. Of course, you would use
Manager URL (/quark/servlet/qxpsm/...) if you are sending a request to Manager.
Related topics:
Getting started: HTTP
Dissecting a QuarkXPress Server URL
Interpreting the QXP Server response
Function overview
Page 34