ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Meigen, Thomas" <T.Meigen@augenklinik.uni-wuerzburg.de>
To: "<ntg-context@ntg.nl>" <ntg-context@ntg.nl>
Subject: Re: ConTeXt on the Mac (TexShop). Problem of a newbie
Date: Fri, 11 Jan 2013 10:58:54 +0000	[thread overview]
Message-ID: <8E16D40C6A36AF46A9050494F6F6A7BB39AEED02@wklex05v.klinik.uni-wuerzburg.de> (raw)
In-Reply-To: <CAF=dkzy3t9eBfMVo8gmmubRgDu329+D8dnzmzyRtrwE7uRy2hw@mail.gmail.com>

Thank you very much for your clarifications!

To summarize...

1. The use of additional modules may be nice (as Sietse proposed the
complex-slides module), but ConTeXt can achieve very flexible solutions
even without these modules.

2. Although the production of slides was not the main issue of my question,
I am amazed by the step-by-step guide from Aditya. This was very helpful
and I learned a lot about ConteXt by going through all the incremental changes.
Thanks!

3. I understand that some presentation styles/modules are provided by users
and that they may have to be adapted for specific applications. At this point I
was a bit surprised that the dependencies between different modules are not
documented explicitly within the modules. E. g., when I tried to use the
"simpleslides" module with the "simpleslides-s-Boxed" layout, I did not find a
"required modules..." command that might have helped to see the problem.
This is different from the LaTeX mechanism to load required packages.
However, the reason might be that LaTeX depends much more on these
packages, so a strict mechanism is mandatory. Anyway, after you get used
to some typical modules in ConTeXt you might not miss this kind of strict rule...

4. The fact that my initial example starting with

> 1 \usemodule[s-pre-05]

crashed for s-pre-05 and most of the other s-pre-XX modules indicates that
such crashes have nothing to do with the decision to load modules from
other users. The s-pre-XX modules are part of the standalone ConTeXt
installation, my installation was fine, but a recent update of some mkiv
component was not compatible with luatex.

So what to do next? Load an earlier ConText version? Wait until this
problem is fixed? If the mkiv <-> luatex interaction is the reason for this
problem, the problems might not be restricted to some s-pre-XX
modules (that are unchanged since about two years...) ?


Thanks again
Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2013-01-11 10:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 15:07 Meigen, Thomas
2013-01-09  9:00 ` Hans Hagen
2013-01-09 16:01   ` Sietse Brouwer
2013-01-10  8:13     ` Meigen, Thomas
2013-01-10  9:11       ` Hans Hagen
2013-01-10 10:47         ` Keith J. Schultz
2013-01-10 11:19           ` Martin Schröder
2013-01-10 11:58             ` Hans Hagen
2013-01-10 12:01           ` Hans Hagen
2013-01-10 11:22         ` Aditya Mahajan
2013-01-10 13:03           ` Aditya Mahajan
2013-01-10  9:22       ` Keith J. Schultz
2013-01-11 10:58     ` Meigen, Thomas [this message]
2013-01-11 13:11       ` Hans Hagen
2013-01-11 11:32     ` Meigen, Thomas
2013-01-11 12:09       ` Khaled Hosny
2013-01-11 13:15       ` Hans Hagen
2013-01-11 23:13         ` Sietse Brouwer
     [not found]     ` <8A5FF695-AC2A-493E-81D6-322090E1B895@klinik.uni-wuerzburg.de>
2013-01-13 22:03       ` Meigen, Thomas
2013-01-13 22:44         ` Hans Hagen
     [not found] <mailman.269.1357821208.2489.ntg-context@ntg.nl>
2013-01-10 14:17 ` Pavneet Arora
2013-01-10 14:23 ` Pavneet Arora

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=8E16D40C6A36AF46A9050494F6F6A7BB39AEED02@wklex05v.klinik.uni-wuerzburg.de \
    --to=t.meigen@augenklinik.uni-wuerzburg.de \
    --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).