project structure

[Hans Hagen <pragma@wxs.nl>]

Hi,

There is a new experimental feature (one of the side effects of 
discussions with Alan about bibliographies and using distributed files 
in a project structure).

Say that you have this:

test1.tex : uses \component one/test2

one/test2.tex : uses \component two/test3

etc. There can be resources under one/two that test3 needs and one way 
out is to add this path to the used paths. Doing that automatically can 
result in side effects when multiple resources with the same name are used.

However, we now have a concept of the local job path, so when test2 is 
read the jobfile: prefix will use path one, and when reading test3, that 
prefix will trigger one/two usage.

For this to work, one has to say:

\usepath[jobfile:]
\setupexternalfigures[directory=jobfile:]

To what extent this all works out well is to be tested.

Hans

ps. file loading related code is somewhat complex because we also need 
to support tds/kpse like searching; normally such more direct lookups 
kick in early (there are more prefixes and urls are also kind of special)


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