From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Modules inside project structure
Date: Wed, 15 Jun 2011 12:01:12 +0200 [thread overview]
Message-ID: <4DF882E8.7010905@wxs.nl> (raw)
In-Reply-To: <13610400819.20110613115007@gmx.de>
On 13-6-2011 11:50, Andreas Schneider wrote:
> I'm currently trying to split our ConTeXt project into smaller parts,
> utilizing the ConTeXt project structure. I thought it might be a good
> idea to also extract reusable parts into private modules. Now I face
> the problem, that I can't find an optimal spot to place these modules.
> Currently I just have them at the root of the project where I also
> have the environment file that is used. That kinda works, since
> \usemodule uses resolvers.findctxfile which also traverses parent
> directories. Unfortunately \registerctxluafile doesn't, so the
> corresponding lua file isn't loaded (which I currently circumvent with
> dofile()).
>
> I guess it might be cleaner to make use of texmf-project or something
> similar, however that would require the "user" (who is working with
> that project) to modify their TeX tree and rebuild their formats. It's
> also a bit strange, since these modules are exclusive to that one
> project - a new project would at least require copies of these files
> anyway. So these modules should preferably lie somewhere beneath the
> actual project, and not "globally" on the system of the user.
>
> What would you suggest to handle such projects that should be
> separated and independent from the ConTeXt installation of the
> "users"? Would you use modules at all in that case?
I always put project specific files in texmf-project. This tree is
standard part of the minimals so there is no need for additional
configuration. One only has to run mtxrun --generate after adding files
(in most cases projects files get changed, not added).
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2011-06-15 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 9:50 Andreas Schneider
2011-06-15 10:01 ` Hans Hagen [this message]
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=4DF882E8.7010905@wxs.nl \
--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).