ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Matt Gushee <mgushee@havenrock.com>
Subject: Re: How to add your own modules?
Date: Mon, 21 Oct 2002 01:32:24 -0600	[thread overview]
Message-ID: <20021021073224.GC545@swordfish> (raw)
In-Reply-To: <5.1.0.14.1.20021020185247.029713a8@remote-1> <16218489316.20021018232816@iol.it> <200210182253.38978.angerweit@gmx.net>

Thank you all for the suggestions.

On Fri, Oct 18, 2002 at 10:53:38PM +0200, Henning Hraban Ramm wrote:

> Not really.
> Your own modules should go into (texmf-var or so)/tex/context/user
> and you should name them t-somewhat.tex (t for "third-party module").
> Then you can address them with \usemodule[somewhat] (without t-).

Is that all you need to do? I have tried that and it's not working. Do
you need to somehow "register" your module with the system or perhaps
generate a format file before using it?

> You can find my two presentation styles at the link below (mostly in 
> german...). One is a "translation" of the PowerPoint company style of my 
> employer, the other my own "corporate" style. They are not sophisticated, but 
> useful.

Thank you. I'll take a look at them.

On Sun, Oct 20, 2002 at 06:54:53PM +0200, Hans Hagen wrote:
> At 11:28 PM 10/18/2002 +0200, Giuseppe Bilotta wrote:
> >
> >You may want to consider using "environments", though, rather than
> >modules, if all you want to do is "tweak" a pre-exisiting module.
> >(I don't know where environment files go, though; I keep them in
> >the root of my ConTeXt document tree, since ConTeXt looks up to
> >two levels up to find environments.)
> 
> let's not end up in thousands of modules; the m- s- p- x- prefixes are used 
> for the core distrubution, the t- is for users, but then you should be 
> aware of potential name clashes with other third party modules; if possible 
> follow GB's suggestion to use environments

That's a good point. I'm certainly in favor of non-invasive
modifications whenever they are possible. I guess I need to learn more
about environments. As long as I'm here, let me just ask: for the
presentation I mentioned last month, the style I used was basically the
Pragma "original" style (from 's-pre-01.tex'); as far as I remember I
didn't change the layout at all, just used different fonts and colors.
Would that be an appropriate task for an environment?

-- 
Matt Gushee                 When a nation follows the Way,
Englewood, Colorado, USA    Horses bear manure through
mgushee@havenrock.com           its fields;
http://www.havenrock.com/   When a nation ignores the Way,
                            Horses bear soldiers through
                                its streets.
                                
                            --Lao Tzu (Peter Merel, trans.)


  reply	other threads:[~2002-10-21  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 20:36 Matt Gushee
2002-10-18 20:53 ` Henning Hraban Ramm
2002-10-21  7:32   ` Matt Gushee [this message]
2002-10-21 10:07     ` Hans Hagen
2002-10-18 21:28 ` [NTG-context] " Giuseppe Bilotta
2002-10-20 16:54   ` 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=20021021073224.GC545@swordfish \
    --to=mgushee@havenrock.com \
    /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).