![]() |
|
need help? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Xtags Server for QuarkXPress Beta DownloadsFirst, you must see important information about beta software if you haven't already. Then, see the latest Xtags for QuarkXPress beta information, all of which applies fully here (and isn't repeated). Then, download one of the following, depending on your platform:
Finally, sample files are available from Xtags sample files. (See notes below on how to use these samples.) We're keeping this version in synchronization with the client Xtags for QuarkXPress releases, down to the bug-fix level (e.g., 7.3.2), and we're trying to keep the beta release levels the same as well, to avoid confusion. The full (and only) documentation for the server aspects of this version is online at the end of this page, for now. Change HistorySee the normal XPress beta page for features added and changed at each beta release.Known limitationsKnown limitations and problems with this release are:
Xtags Server for QuarkXPress UsageThe Xtags Server 6.x/7.x XTension is an enhanced version of the corresponding Xtags 6.x/7.x XTension, with exactly the same core features, but with additional logic for operating in the QuarkXPress Server 7 (QuarkDDS 3.5+) environment, and minus its normal user interface. (Preferences are controlled at invocation time by URL/form parameters.)PrerequisitesBefore you can use this information effectively, you must understand the basics of installing, administering and using QuarkXPress Server as a web service, since we can't really cover that all that here. (QuarkXPress Server is called QuarkDDS in its current 3.5+ incarnation (corresponding to QuarkXPress 6.5+), and QuarkXPress Server in its 7.x incarnation.)Installation(This needs to be updated for QuarkXPress Server 7.)
To install Xtags Server, shutdown QuarkDDS if it's running, download
and extract the XTension file (named OperationTo invoke Xtags in the server environment, you use only one of the following Xtags URL parameters (or HTML form parameters) along with an otherwise standard DDS request:
Xtags will attempt to find the autoflow text stream on the first page in the document being rendered, and import its input stream into that set of text boxes (one or more--contents are assumed to be empty). If it can't find an autoflow stream, it will fail with an appropriate error message. (This means any Xtags-driven templates must have an autoflow text chain, even if it's just a tiny "toe hold" invisible (no background color, no runaround) text box somewhere on the master page.) The general intent with both of these control parameters is that Xtags will do its normal document-building with the given input, and then XPress Server will render the results. For example, the simple URL (where
asks DDS to render the document mydoc.qxd as a JPEG
graphic, after giving Xtags as input the characters "Hello world."
(Awfully simple, but you get the idea.) Of course, in most cases,
you'd send xtagsinputtext as an encoded HTML form <input
type="text"> parameter of any length and content.
For another example, using xtagsinputfile, the URL (ignoring any line wrapping here)
asks DDS to render the document myfiles/mydoc.qxd as a
PDF file, after giving Xtags as input the contents of the file
builddoc.xtg found in the myfiles folder
under the DDS document pool top-level folder (e.g., under Mac OS X,
the actual input file would be something like
em10:Applications:QuarkDDS 3.5:QuarkDDS
Documents:myfiles:builddoc.xtg, and under Windows,
c:\Program Files\Quark\QuarkDDS 3.5.3\QuarkDDS\QuarkDDS
Documents\myfiles\builddoc.xtg). Of course, use of
xtagsinputfile presumes you've managed to get that file
uploaded to the server somehow.
Three boolean (value "1" for yes, or "0" for no) parameters control Xtags' operation (these are the same as the UI preferences):
So, for example, the URL (again, ignoring any line wrapping)
will render mydoc.qxd using the given Xtags input file,
with quote conversion off, error reporting on, but with picture errors
suppressed.
Xtags picture creation tag file paths (and translation tables) are looked up normally, using either absolute or relative paths. Relative paths are evaluated in the following order:
The general idea is that you can, in the server request HTML POST form, supply all text and graphics needed to build the current document, without reference to external files. You can also upload all graphics and text input files to somewhere in the document pool and reference them relatively. Or, you can mix and match these two approaches at will. Using the Sample Files With the sample files
downloaded, unpack the .zip archive, and copy or move the
As a simple but complete end-to-end test that the files are in place and the Xtags Server XTension is working, click this link: http://localhost:8080/jpeg/xtags/Demo%20template.qxd?xtagsinputfile=xtags/Basic%201.txtwhere you may have to replace "localhost:8080" with your XPress Server hostname/IP address and port. You should see a page of (single large JPEG) output (that produced by importing the xtags/Basic 1.txt Xtags file into the Demo
template.qxd template document. Try tacking a
&page=2 on the end of this URL to see the second page (just
a handful of lines, normally).
Then, move or copy the sample file .zip archive's
As another demonstration, you can build documents and retrieve results entirely from the command line, using utilities like "curl". For example, in Terminal under Mac OS X, you can use something like
to create and view the JPEG file resulting from processing the given Xtags input text with the given template. Host and System RequirementsXtags 6.x Server requires QuarkDDS 3.5 or later (3.5.2 recommended); Xtags 7.x Server requires QuarkXPress Server 7.0 or later under Mac OS X or Windows. Xtags Server of any version has no additional system requirements beyond that of its host.
|
$400
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
top | home
© 2005 em software, inc. all rights reserved.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||