ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Keith McKay <mckaymeister@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Entering text into layers
Date: Tue, 20 May 2014 09:10:47 +0100	[thread overview]
Message-ID: <537B0E07.1010002@gmail.com> (raw)
In-Reply-To: <26770461-53B2-43D0-BB84-610D186EB244@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1761 bytes --]

Thanks Wolfgang

This is really useful and something I will give further study to.

Thanks again for your help.

Best Wishes
Keith

On 19/05/2014 22:54, Wolfgang Schuster wrote:
>
> Am 19.05.2014 um 17:43 schrieb Keith McKay <mckaymeister@gmail.com 
> <mailto:mckaymeister@gmail.com>>:
>
>> Colleagues
>>
>> I have been designing a simple document which comprises of 4 areas (3 
>> for text, 1 for images) on an A4 page.  I thought that the best way 
>> to do this would be using Layers and so far I come up with the code 
>> below after scanning the wiki. As you can see it is not very 
>> sophisticated, but I'm not a regular user of Context.  The question I 
>> have is what would be the best way to add text to the various 
>> layers?  Some would have quite a lot of text and I was wondering if 
>> would be better to define the text for the different layers in some 
>> way rather than enter into the braces of \setlayerframed.  The code 
>> would look messy this way. Finally, can layers be positioned within 
>> layers or would it be better to use overlays?  I'm thinking about 
>> adding three columns to the Footer layer.
>
> A short description about layers and overlays: 
> http://www.ntg.nl/pipermail/ntg-context/2013/070935.html
>
> Wolfgang
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 3821 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2014-05-20  8:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 15:43 Keith McKay
2014-05-19 21:45 ` Hans Hagen
2014-05-20  8:07   ` Keith McKay
2014-05-20  8:12     ` Hans Hagen
2014-05-19 21:54 ` Wolfgang Schuster
2014-05-20  8:10   ` Keith McKay [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=537B0E07.1010002@gmail.com \
    --to=mckaymeister@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).