ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Automating a letter module style
Date: Mon, 25 Nov 2002 18:23:57 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20021125181735.027ece20@server-1> (raw)
In-Reply-To: <C6CF5D04-0098-11D7-9C5E-0030657A7050@fastmail.fm>

At 12:10 PM 11/25/2002 -0500, Bruce D'Arcus wrote:

>On Monday, November 25, 2002, at 11:58 AM, Hans Hagen wrote:
>
>>a user interface to processing tex docs, based on pdf, controlled by a 
>>tex-applet; think of entering your letter text and data in a form, 
>>pushing a button and getting a letter back (this is just one application, 
>>we also use it to make enveloppes and alike); click and point layout 
>>options, etc; works quite well; to tease you again, this is just part of 
>>a bigger game -)
>
>Hmm...interesting indeed!  Just to prod a bit more, though, what kind of 
>UI, and entered into what kind "form"?  I won't ask about the "bigger game" :-)

i let tex generate a document with fields that a user can fill in; that way 
you get a platform independent interface; the submits this data to a 
servlet, which, based on the embedded request, takes some action; after a 
while a pdf doc is send back; the document is (yet) coded in tex (rather 
high level interface macros), the request specific scripts are coded in xml 
as is the whole environment in which this takes place; communication takes 
place in xml as well.

[i may add an xml user interface to the tex part as well, when i'm in the mood]

>This may or may not be relevant, but any chance as you work on this stuff 
>XML might enter the picture as an alternate coding approach?

xml already has entered the picture since we use it for processing tex and 
xml docs

Hans

-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

  reply	other threads:[~2002-11-25 17:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21  0:00 Nigel King
2002-11-21 14:40 ` John Culleton
2002-11-21 15:23 ` Bruce D'Arcus
2002-11-22 22:31   ` Hans Hagen
2002-11-22 23:40     ` Bruce D'Arcus
2002-11-25 16:58       ` Hans Hagen
2002-11-25 17:10         ` Bruce D'Arcus
2002-11-25 17:23           ` Hans Hagen [this message]
2002-11-29 11:36         ` metafun and \input graph Hartmut Henkel
2002-11-29 12:53           ` Nigel King
2002-11-29 12:58           ` Hans Hagen
2002-11-29 16:55             ` Hartmut Henkel
2002-11-29 17:12               ` Hans Hagen
2002-11-22 23:14 ` Automating a letter module style Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.1.20021125181735.027ece20@server-1 \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).