From: Christian Egli <christian.egli@sbs.ch>
To: emacs-orgmode@gnu.org
Subject: Re: Question: split up files for subprojects using taskjuggler-export (tj3)
Date: Wed, 22 Feb 2012 11:39:38 +0100 [thread overview]
Message-ID: <87boorp2xh.fsf@sbs.ch> (raw)
In-Reply-To: 8a6811f6c1551d4e607d0794e29b5f0d@dittmaridoo.de
Hi
mail@dittmaridoo.de writes:
> I am looking for a solution to split one project into sub-projects, so
> I can distribute the project into sub-files as suggested here:
> http://groups.google.com/group/taskjuggler-users/browse_thread/thread/a98489a0e343ddac
The export of org-mode to taskjuggler can be taken pretty far and can
handle big projects. It is meant for people comfortable with org-mode
that like to work within org-mode. However not all concepts in org-mode
for example have a corresponding concept in taskjuggler and vice versa.
The exporter tries to bridge this mismatch in some cases and ignores
others.
So, what I'm saying is that if you want the full power of taskjuggler
then by all means go for it (i.e. hack your stuff in it directly). If
you want the convenience of org-mode then stay with it and try to
organize the project within org-mode. IMHO using org-mode lessens the
need to structure the projects into sub-files as org-mode is less
verbose and inherently more structured.
If you still would like to split you project some more I'd try to do
something using (tj) include statements, e.g. defining them as your
default reports.
Hope that helps.
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
prev parent reply other threads:[~2012-02-22 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 17:40 Question: split up files for subprojects using taskjuggler-export (tj3) mail
2012-02-22 10:39 ` Christian Egli [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87boorp2xh.fsf@sbs.ch \
--to=christian.egli@sbs.ch \
--cc=emacs-orgmode@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).