From 5f2039396f9e5ceccb06d47896c2df45df1cdb51 Mon Sep 17 00:00:00 2001 From: dchandler Date: Sat, 22 Mar 2003 02:53:35 +0000 Subject: [PATCH] Removed most mentions of QuillDriver and Savant from this file. --- htdocs/BuildSystems.html | 66 +++++++++++++++++++++------------------- 1 file changed, 34 insertions(+), 32 deletions(-) diff --git a/htdocs/BuildSystems.html b/htdocs/BuildSystems.html index 8250d07..31b5869 100644 --- a/htdocs/BuildSystems.html +++ b/htdocs/BuildSystems.html @@ -14,14 +14,15 @@

THDL Tools Build Systems

- David Chandler has put together a build system for Jskad, Savant, - QuillDriver, the translation tool, Tibbibl, and for the fonts. This - document describes them, and should be updated if we put together - build systems for the two diacritics packages and for Wylie Word - (but see e-mail to thdl-devel@lists.sourceforge.net that tells why - we probably will continue to require Wylie Word developers to edit - from within MS Word on account of the difficulty of using CVS with - VBA). + David Chandler has put together a build system for Jskad, the + translation tool, Tibbibl, and for the fonts. In the CVS + repository, you'll find that the build system once worked for Savant + and QuillDriver as well. This document describes them, and should + be updated if we put together build systems for the two diacritics + packages and for Wylie Word (but see e-mail to + thdl-devel@lists.sourceforge.net that tells why we probably will + continue to require Wylie Word developers to edit from within MS + Word on account of the difficulty of using CVS with VBA).

What is a build system, you ask? A build system is a set of @@ -237,8 +238,9 @@ by the Venus Application Publisher. You need this to cut Java Web - Start releases of Jskad, Savant, QuillDriver, and the - translation tool. You do not need it otherwise. + Start releases of Jskad, [Tibbibl if I ever get my act + together], and the translation tool. You do not need it + otherwise.

Installing Vamp's Ant task is simple enough, and is in fact @@ -443,8 +445,8 @@ module Not all of the material up at our SF.net website is in the www CVS module, but most of it is. Currently, the only - exception is the Javadoc API documentation for Jskad, Savant, - QuillDriver, and the translation tool. + exception is the Javadoc API documentation for Jskad, Tibbibl, and + the translation tool.

@@ -598,7 +600,7 @@ module

The first thing to note is that the Jskad module is misnamed. We have all our Java code inside this module, including - Jskad, Savant, QuillDriver, and the translation tool. + Jskad, Tibbibl, and the translation tool.

@@ -646,7 +648,7 @@ module builds that also requires XSLT (i.e., the presence of those JARs, but in a place that Ant recognizes).  A consequence of using this location is that you'll probably find using targets like - qd-run much easier than specifying your own + jskad-run much easier than specifying your own CLASSPATH. @@ -697,7 +699,7 @@ module

This section describes how our build system interacts with your - daily work hacking on Jskad, Savant, QuillDriver, and the + daily work hacking on Jskad, Tibbibl, and the translation tool.

@@ -752,13 +754,13 @@ module

Running the tools is easy for a developer. Just run 'ant program-run', where program is one of - jskad, tt, savant, or - qd. This deals with classpaths and all of that, and it - compiles beforehand if needed. Note the gotcha above if you're - rerunning after changing the source code -- you'll have to use - 'ant clean program-run'. If you modify a - resource, such as Jskad/source/options.txt, there are - no gotchas -- Ant is smart enough to handle this. + jskad, tt, or tibbibl. This + deals with classpaths and all of that, and it compiles beforehand if + needed. Note the gotcha above if you're rerunning after changing + the source code -- you'll have to use 'ant clean + program-run'. If you modify a resource, such as + Jskad/source/options.txt, there are no gotchas -- Ant + is smart enough to handle this.

@@ -872,8 +874,8 @@ module

Java Web Start makes it possible (in theory, anyway) to install a complex - application like Savant with one mouse click of a link in your - favorite web browser and one more click of a "Yes, install Savant" + application like Jskad with one mouse click of a link in your + favorite web browser and one more click of a "Yes, install Jskad" button in a dialog box (necessary because our applications require security privileges to read and write from disk etc.). Upon the second run of the program, Java Web Start asks the user if they want @@ -986,9 +988,9 @@ module     program-jws'

- where program is one of jskad, tt, - savant, or qd. This cleans first, so your - changes will be respected. This then creates a WAR file + where program is one of jskad or + tt. This cleans first, so your changes will be + respected. This then creates a WAR file Jskad/dist/java-web-start/program-JWS.war. This also extracts the signed JAR from inside that WAR, which is handy if you're deploying to a web server that isn't running a J2EE @@ -1048,11 +1050,11 @@ module

You're done! Except, of course, for the gotcha: At present, only the translation tool and Jskad have working Java Web Start - releases; Savant's and QuillDriver's are on the way. Savant and - QuillDriver, like Jskad, requires all-permissions security. That - means that xalan.jar, xercesImpl.jar, and - xml-apis.jar need to be jar-signed by the same - certificate as QuillDriver. We do this automatically via 'ant + releases; Tibbibl's is on the way. Tibbibl, like Jskad, requires + all-permissions security. That means that xalan.jar, + xercesImpl.jar, and xml-apis.jar [or + whichever subset is used...] need to be jar-signed by the same + certificate as Tibbibl. We do this automatically via 'ant self-contained-dist' or 'ant web-start-releases', but here's how to do this manually: