From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: thomas.schmitz@uni-bonn.de
Subject: Re: prezi presentations
Date: Tue, 9 Apr 2013 16:16:53 +0200 [thread overview]
Message-ID: <20130409161653.63e01e73@sole> (raw)
In-Reply-To: <516403DC.3070901@uni-bonn.de>
On Tue, 9 Apr 2013 14:04:44 +0200
"Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de> wrote:
> Hi all,
>
> this is a very far shot, but just maybe... I have been looking at prezi
> (http://prezi.com/). There's lots of aspects there that don't appeal to
> me, but I find the general idea very nice: a presentation is sort of a
> big poster, with some background graphics. You define areas on this
> poster into which your content goes (so these would be the "slides" in a
> conventional presentation). When you show your presentation, your viewer
> will zoom in on these areas and present them full screen, and it will
> move along a predefined path, thus showing the areas (slides) in a
> certain order. The nice thing is that you can, at any moment, zoom out
> and show the entire poster, thus giving an overview of your presentation
> in which only the bigger elements (headlines etc.) will be readable. Now
> I was wondering if the same couldn't be done with ConTeXt, pdf and
> javascript: producing a big pdf with a background image would be fairly
> easy (metapost's vector graphics would look good at any zoom level).
> Placing slides with content there could be done via layers. Zooming in
> and showing certain areas is doable (but obviously would depend on the
> pdf viewer, especially for the full screen mode). I have no idea if we
> have support for rotating areas in a pdf viewer. Would javascript be
> capable of automating this, i.e. defining areas in a pdf, displaying
> them at a certain zoom level, and move from one area to the next? I
> think this would be a nice alternative to traditional slide shows.
>
> Thomas
Very fashionable, phluffy, breaks the ice at parties...
I sat through a prezi presentation recently. The speaker took us on a
long trip. It was "cool"! But in the end, there was not much to retain,
and I thought: "where's the beef?".
As to the constant zooming in and out, I kept wondering what the little
specks represented (that I knew we would soon be visiting). Sort of like
the old transparency technique of hiding parts with paper flaps. Lots of
suspense! :)
Remember, viewed from afar, all organisms look just like flies.
For further discussion, I suggest:
http://www.edwardtufte.com/tufte/books_pp
Alan
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-04-09 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 12:04 Thomas A. Schmitz
2013-04-09 14:14 ` sozi presentations Romain Diss
2013-04-09 14:22 ` Mojca Miklavec
2013-04-09 20:09 ` Marcin Borkowski
2013-04-09 14:16 ` Alan BRASLAU [this message]
2013-04-09 14:24 ` prezi presentations luigi scarso
2013-04-09 18:47 ` Hans Hagen
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=20130409161653.63e01e73@sole \
--to=alan.braslau@cea.fr \
--cc=ntg-context@ntg.nl \
--cc=thomas.schmitz@uni-bonn.de \
/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).