Hello,

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?

-- 
Best Regards,
Andreas

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

Reply via email to