From: "Alan Stone" <software.list.1es9s@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: \*interaction* commands
Date: Wed, 30 Jul 2008 09:55:46 +0200 [thread overview]
Message-ID: <326847810807300055x2e083942ha8589b2813345064@mail.gmail.com> (raw)
In-Reply-To: <488F7A51.60607@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1582 bytes --]
>you can run layo-05.tex with --mode=demo to get a simple example, given
>at the bottom of that file
I guess you mean s-pre-05.tex Hans.
Best,
Alan
On Tue, Jul 29, 2008 at 10:15 PM, Hans Hagen <pragma@wxs.nl> wrote:
> Alan Stone wrote:
> > I'm still trying to reproduce the layo-05.tex example Hans. As its code
> > is rather tortuous I studied other examples. Up till now this has been
> > quite a time investment without noticeable return, partly due to not
> > finding a comprehensive \*interaction* commands documentation to
> > guide me all along.
>
> the problem with interaction is that there is not one route ... the
> simplest way is to just turn it on (\setupinteraction[state=start])
>
> next there are only a few special interaction things: goto, buttons and
> menus and it really depends on your design then what you use
>
> the other thingies (graphics and such) ar enot special to interaction
>
> you can run layo-05.tex with --mode=demo to get a simple example, given
> at the bottom of that file
>
> an option is to copy that file into a temp one and start commenting ...
> that way you see what happens; normally a style is built the other way
> around,
>
> - set up a papersize
> - adapt the layout
> - start keying some text
> - then see what kind of text you have
> - adapt your design to the content
>
> now, esp with things like menus, finetuning really depends on the kind
> of content; the best way to get a feeling for that is just try things
> (at least that's how i do it ... just try what looks best as there is no
> recipy for a design)
>
> Hans
>
[-- Attachment #1.2: Type: text/html, Size: 2048 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-07-30 7:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 13:28 Alan Stone
2008-07-29 15:29 ` Taco Hoekwater
2008-07-29 15:49 ` Alan Stone
2008-07-29 17:52 ` Hans Hagen
2008-07-29 18:28 ` Alan Stone
2008-07-29 20:15 ` Hans Hagen
2008-07-30 7:55 ` Alan Stone [this message]
2008-07-30 8:07 ` Hans Hagen
2008-07-30 15:50 ` Alan Stone
2008-07-30 16:18 ` 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=326847810807300055x2e083942ha8589b2813345064@mail.gmail.com \
--to=software.list.1es9s@gmail.com \
--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).