ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <gesang@stud.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: A "Lorem ipsum" module?
Date: Wed, 18 Jul 2012 13:33:17 +0200	[thread overview]
Message-ID: <20120718113317.GA29669@phlegethon> (raw)
In-Reply-To: <20120718114228.3a6d5651@aga-netbook>


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

Hey Marcin,

···<date: 2012-07-18, Wednesday>···<from: Marcin Borkowski>···

> If not (as I suspect), what should I do to write such a module?  I
> expect this shouldn't be too difficult, and I could learn a few things
> (like using key-value syntax in ConTeXt, for instance); are there any
> recommendations for people wanting to learn to write a (simple) module
> for ConTeXt (other than the relevant wiki page)?  For example, which
> existing modules might I want to take and read the source code of?

Wolfgang’s fancybreak module is a good place to start, because it
demonstrates the current namespace syntax quite nicely. Also, it
is very specific wrt functionality, so it can be understood
completely by just reading the code. (Of course you should be
familiar with the module from a user perspective but that’s no
effort.)

  https://bitbucket.org/wolfs/fancybreak/src/20ec76c5e154/files/t-fancybreak.mkvi

Happy TeXing!
Philipp

> 
> Best,
> 
> -- 
> Marcin Borkowski
> http://mbork.pl
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 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
___________________________________________________________________________________

  parent reply	other threads:[~2012-07-18 11:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18  9:42 Marcin Borkowski
2012-07-18 10:18 ` Marco
2012-07-18 11:33 ` Philipp Gesang [this message]
2012-07-19  1:27 Rogers, Michael K
2012-07-19  5:30 ` Henning Hraban Ramm
2012-07-19 11:08 ` Hans Hagen
2012-07-19 14:42   ` Marco
2012-07-19 14:52     ` Wolfgang Schuster
2012-07-19 14:59       ` luigi scarso
2012-07-19 15:17   ` Marco
2012-07-19 23:20   ` Sietse Brouwer

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=20120718113317.GA29669@phlegethon \
    --to=gesang@stud.uni-heidelberg.de \
    --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).