From: Marco Kuhlmann <mk@mcqm.net>
Subject: Re: Modules
Date: Sat, 19 Jan 2002 18:17:13 +0000 [thread overview]
Message-ID: <20020119181713.GA6129@localhost> (raw)
In-Reply-To: <87pu46dxk9.fsf@dellius.nederware.nl>
* Berend de Boer <berend@pobox.com> (2002-01-19 19:07:18 +0100):
> 1. What is a well-defined module interface? You have \usemodule. A
> module is just any ConTeXt file for now.
Exactly. But what about
- module parameters
- standard \setup keywords
- namespaces
- usage of standard library macros
> 2. You can use any ConTeXt code, why should a module be limited?
For portability reasons, for example. If there were some kind
of standard library, then one would rather want to use that
instead of self-hacked things, because it will still work and
the sizes of the modules will be smaller. Of course, in
general, you can do whatever you want. This is merely a
question of maintenance and system integrity -- which LaTeX
lacks, for example.
> 3. Distribution mechanism isn't there, but I'm sure Hans is quite
> willing to put up links on his ConTeXt page to 3rd party
> stuff. Perhaps a good idea, what do you think Hans?
It certainly would be. However, it should also be on CTAN. And
Giuseppe's comments on things like TeXUtil hooks etc. are worth
considering, in my opinion.
Marco
next prev parent reply other threads:[~2002-01-19 18:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 21:57 Modules Marco Kuhlmann
2002-01-18 18:30 ` Modules Giuseppe Bilotta
2002-01-19 23:20 ` Modules Hans Hagen
2002-01-21 10:13 ` Modules Taco Hoekwater
2002-01-21 14:31 ` Re[2]: Modules Giuseppe Bilotta
2002-01-21 18:07 ` Berend de Boer
2002-01-22 9:38 ` Re[4]: Modules Giuseppe Bilotta
2002-01-21 14:47 ` Modules Hans Hagen
2002-01-22 9:10 ` Modules Taco Hoekwater
2002-01-22 11:03 ` Modules Eckhart Guthöhrlein
2002-01-19 18:07 ` Modules Berend de Boer
2002-01-19 18:17 ` Marco Kuhlmann [this message]
2002-01-20 16:03 ` Re[2]: Modules Giuseppe Bilotta
2002-01-20 22:04 ` Modules Hans Hagen
2002-01-20 21:57 ` Modules Hans Hagen
2002-01-20 20:05 ` Modules Hans Hagen
2006-04-04 8:02 modules Hans Hagen
2006-08-08 23:33 ` modules Nikolai Weibull
2006-08-09 1:53 ` modules Sanjoy Mahajan
2006-08-09 7:08 ` modules Taco Hoekwater
2006-08-09 8:38 ` modules Nikolai Weibull
2006-08-09 10:16 ` modules Hans Hagen
2006-08-09 10:21 ` modules Taco Hoekwater
2006-08-09 11:57 ` modules Nikolai Weibull
2006-08-09 12:07 ` modules Taco Hoekwater
2006-08-09 12:28 ` modules Nikolai Weibull
2006-08-10 14:06 ` modules Patrick Gundlach
2008-08-06 8:37 modules luigi scarso
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=20020119181713.GA6129@localhost \
--to=mk@mcqm.net \
/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).