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 -----------------------------------------------------------------