ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marco Kuhlmann <mk@mcqm.net>
Subject: Modules
Date: Thu, 17 Jan 2002 21:57:48 +0000	[thread overview]
Message-ID: <20020117215748.GA762@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 2219 bytes --]

    Today I got into trouble.

In summer, I have started what I thought would be my transition
from LaTeX to ConTeXt. It all seemed so obvious: ConTeXt is
richer in features, has much cleaner code, and there's a lot of
innovation. And if I had a problem, or even a feature request,
I could just write to you all.

Today my view of things got challenged. I must admit that the
cause (though not the causing) for my doubts is my
disappointment with the math module on the one hand, and the 
pressure that I put onto myself to convert my society's macro
collections into ConTeXt on the other. However, here they are:

One of the strengths of LaTeX is the number of add-on packages
available for it. Of course, this also is one of its
weaknesses: there is a lot of overhead, some packages do not
interact well with each other, there are a lot of developers
with different styles, etc. When I prepared my first book using
ConTeXt, I was amazed to see that everything got so simple.

However, I wonder if not ConTeXt needs some of that LaTeX
feeling. In LaTeX, when you miss a feature, you know that there
is a package out there that implements it. In ConTeXt, you ask
Hans et al. Why are there so few modules?

It may of course be due to the relatively small number of
users. However, one important reason in my opinion is the lack
of a well-defined module interface. How should modules be
designed? Is there a standard library of functions that they
could or should use? If I wrote a new module, how would I
distribute it (for LaTeX, I would use CTAN)?

What I propose it that we should think about going public.
ConTeXt has so much to offer, it should become more widely
used. A promising way to achieve this is to get more and more
people involved in enhancing and documenting it. That does not
say, of course, that base ConTeXt could and should not remain
in the hands of PRAGMA. But an active community of developers
working on extensions to the core is a good thing. And if it is
well organised, it does not have to threaten the integrity of
the system as a whole.

    What do you think?
    Marco

-- 
Marco Kuhlmann                 http://www.ps.uni-sb.de/~kuhlmann/

[-- Attachment #2: Type: application/pgp-signature, Size: 248 bytes --]

             reply	other threads:[~2002-01-17 21:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 21:57 Marco Kuhlmann [this message]
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   ` Modules Marco Kuhlmann
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=20020117215748.GA762@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).