ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Presentations
Date: Mon, 3 Apr 2017 13:55:53 -0700 (PDT)	[thread overview]
Message-ID: <alpine.OSX.2.02.1704031350580.10876@nqv-znpobbx> (raw)
In-Reply-To: <757CB337-F713-44B2-8BB2-B49B7567458D@fa.uni-tuebingen.de>

On Mon, 3 Apr 2017, Mathias Schickel wrote:

> Dear ConTeXt users,
>
> me again. I tried to send this emails before, but it seemed to be 
> blocked, because I attached a sample file that seemed too big.
>
> This time I have a question concerning presentations. I was not able to figure out how I can define presentation steps in a way that each step is shipped as a single PDF page in the output. By this I mean steps in one slide that unfold step by step by moving on to the next pdf page. (This means one slide is represented in the PDF as a whole bunch of pages.)
> The command \StartSetps and \FlushStep does something like that, but this seems to use some JAVA script magic that only works using Adobe Acrobat (and the steps are unfolded by hitting the mouse button and not by going on to the next PDF page).
> How can it be modified in a way that a new page per step is created containing the next step in a way that going to the next pdf page unfolds the next step?

I use a personal module to get this behavior. It is not as feature rich as 
beamer's \pause (you need to manually annonate stuff using \STEP 2 { ... } 
etc.; but it serves my purpose). Have a look at some of my recent 
presentations at http://www.ece.mcgill.ca/~amahaj1/talks.html for 
examples.

If this is something that you are looking for, see 
https://www.mail-archive.com/ntg-context@ntg.nl/msg83683.html for the 
code.

Aditya
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2017-04-03 20:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03 19:13 Presentations Mathias Schickel
2017-04-03 20:55 ` Aditya Mahajan [this message]
2017-04-04  6:48   ` Presentations Mathias Schickel
  -- strict thread matches above, loose matches on Subject: below --
2008-08-13 17:58 presentations Hans Hagen
2003-08-18 10:18 Presentations Eduardo Cassiraga
2003-08-18 10:39 ` Presentations Giuseppe Bilotta
2003-08-06  6:52 Presentations Eduardo Cassiraga
2002-02-25  9:49 presentations Piotr Kopszak
2002-02-25 12:05 ` presentations Hans Hagen
2001-10-30 17:51 presentations Patrick Gundlach
2001-10-31  8:58 ` presentations Hans Hagen
2000-04-29  4:26 Presentations David Arnold
2000-04-29  4:51 ` Presentations Johannes Hüsing

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=alpine.OSX.2.02.1704031350580.10876@nqv-znpobbx \
    --to=adityam@umich.edu \
    --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).