ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: Moving to ConTeXt
Date: Fri, 11 Mar 2005 18:02:48 +0100	[thread overview]
Message-ID: <1b64ba7ad08309808fbc6c998684ae56@fiee.net> (raw)
In-Reply-To: <61056.213.84.141.31.1110448760.squirrel@213.84.141.31>

Am 10.03.2005 um 10:59 schrieb Gerben Wierda:
> What I do not understand is how these components end up in a directory
> hierarchy.
>
> What would be very nice is some sort of downloadable archive with some
> sample basic project structures.
>
> Reading the stuff above I still have no idea how to build a directory
> hierarchy for my project such that it can do all that the project
> management part of ConTeXt promises.

Do you *need* different directories? Perhaps it's sufficient to name 
your components so that you can easily see what belongs where.

AFAIK ConTeXt looks always into the parent directories, but not in 
parallel/child directories if not explicitly specified. (E.g. you can 
define a figures path.)

Did you have a look at the wiki: 
http://contextgarden.net/Project_structure


Grüßlis vom Hraban!
---
http://www.fiee.net/texnique/
http://contextgarden.net

  reply	other threads:[~2005-03-11 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22 15:21 Gerben Wierda
2005-02-23 14:46 ` Hans Hagen
2005-02-23 15:13   ` Adam Lindsay
2005-03-10  9:59   ` Gerben Wierda
2005-03-11 17:02     ` Henning Hraban Ramm [this message]
2005-03-11 20:49       ` Gerben Wierda
2005-03-11 20:58         ` Matthias Weber
2005-03-11 21:06           ` Gerben Wierda
2005-03-13 21:28       ` h h extern

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=1b64ba7ad08309808fbc6c998684ae56@fiee.net \
    --to=hraban@fiee.net \
    --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).