ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Margin rules
Date: Mon, 17 Mar 2003 09:14:20 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20030317091118.03941870@server-1> (raw)
In-Reply-To: <000b01c2e8f7$97a2f300$6401a8c0@victorfi>

At 05:50 PM 3/12/2003 +0300, you wrote:
>Hello, Hans!
>
>One year ago you and Giuseppe Bilotta talked about
>margin rules:
>
>GB>> You can set the level, but you cannot customize its
>GB>> color/position/etc, which is what I was talking about.
>
>HH> i can easily implement that (with cross page support and so),
>HH> but definitely not today; so put it on the wish list and
>HH> ask me again later
>
>Let me remind you of this topic, it is very necessary
>for me too.
>
>Or, may be, there is another way to draw vertical lines at left
>of some paragraphs with possibility of crossing page boundaries?

Hm, i thought that i posted something some time ago, but maybe it was not 
to the list.

Can you download the latest beta? It now has a module m-plus:

%D Somewhere in 2001 i started collecting new functionality
%D in a module \type {m-yesno}. As the name suggests, I was
%D not entirely sure if this functionality belonged in the
%D kernel. When (again) on the \CONTEXT\ list a request for
%D side bars was posted, I decided to move such code to plus
%D modules. Users who want this additional functionality can
%D put the following call in their \type {cont-sys.tex} file:
%D
%D \starttyping
%D \usemodule[plus]
%D \stoptyping

This loads:

%D \definesidebar[whow][rulecolor=green,distance=]
%D
%D \starttext
%D
%D \input tufte \par
%D \startsidebar
%D   \input tufte \par
%D   \input tufte \par
%D   \startsidebar[whow]
%D     \input tufte \par
%D     \input tufte \par
%D     \input tufte \stopsidebar \par
%D   \input tufte \par
%D   \input tufte \stopsidebar \par
%D \input tufte \par
%D \input tufte \par
%D \startsidebar
%D   \input tufte \par
%D   \input tufte \par
%D   \input tufte \par
%D   \input tufte \par
%D   \input tufte \stopsidebar \par
%D \input tufte \par
%D \input tufte \par
%D \startsidebar
%D   \input tufte
%D   \input tufte
%D   \input tufte
%D   \input tufte
%D   \input tufte
%D \stopsidebar

and

%D We now reimplement the margin rules handler defined in
%D \type {core-rul}:
%D
%D \setupmarginrules[level=5]
%D
%D \startmarginrule[1]
%D First we set the level at~5. Next we typeset this first
%D paragraph as a level~1 one. As expected no rule show up.
%D \stopmarginrule
%D
%D \startmarginrule[5]
%D The second paragraph is a level~5 one. As we can see here,
%D the marginal rule gets a width according to its level.
%D \stopmarginrule
%D
%D \startmarginrule[8]
%D It will of course be no surprise that this third paragraph
%D has a even thicker margin rule. This behavior can be
%D overruled by specifying the width explictly.
%D \stopmarginrule

There are some moreplus modules, bit not yet suited for usage.

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

  reply	other threads:[~2003-03-17  8:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 14:50 Victor Figurnov
2003-03-17  8:14 ` Hans Hagen [this message]
2003-03-18  4:19   ` Victor Figurnov
2003-03-18  7:40     ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2002-03-09 20:42 Giuseppe Bilotta
2002-03-09 22:04 ` Berend de Boer

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=5.1.0.14.1.20030317091118.03941870@server-1 \
    --to=pragma@wxs.nl \
    --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).