From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Info about creating modules for beginners.
Date: Sun, 26 Sep 2010 11:41:20 -0400 [thread overview]
Message-ID: <03264AD3-8D11-48B8-B51A-654A66891029@umich.edu> (raw)
In-Reply-To: <83FF9D17-32ED-42AB-9AC4-8D17B30D0658@gmail.com>
On Sep 26, 2010, at 10:06 AM, Wolfgang Schuster <schuster.wolfgang@googlemail.com> wrote:
>
> Am 26.09.2010 um 02:02 schrieb Aditya Mahajan:
>
>> Does it make sense to copy the definition of mult-aux.mkiv to mkii? Everything other than \definenamespace should work in both mkii and mkiv. That way, I can use it in modules that target both mkii and mkiv.
>
> Parameter handling is different in mkii and mkiv and it’s not such a problem to write different code for each of them.
But right now, I use a unified parameter handling for both mkii and mkiv.
> For fancybreak i used different mechanism for each of them and i think you should do this as well with your filter module.
You are essentially maintaining two modules, one for mkii and one for mkiv. At least for the filter module, I would like to maintain only one module. The current version has manual parameter handling. Some of which can be automated using \installparameterhandler etc. That is why I am asking part of mult-aux.mkiv to be copied to mkii.
Aditya
___________________________________________________________________________________
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:[~2010-09-26 15:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 16:35 Jaroslav Hajtmar
2010-09-23 20:32 ` Hans Hagen
2010-09-23 20:42 ` Steffen Wolfrum
2010-09-23 20:47 ` Wolfgang Schuster
2010-09-23 21:08 ` Steffen Wolfrum
2010-09-23 21:15 ` Hans Hagen
2010-09-23 21:15 ` Wolfgang Schuster
2010-09-23 21:21 ` Aditya Mahajan
2010-09-23 21:38 ` Wolfgang Schuster
2010-09-23 21:42 ` Aditya Mahajan
2010-09-23 21:46 ` Wolfgang Schuster
2010-09-24 4:26 ` Aditya Mahajan
2010-09-24 7:04 ` Peter Münster
2010-09-23 21:30 ` Steffen Wolfrum
2010-09-23 21:36 ` Jaroslav Hajtmar
2010-09-23 21:43 ` Wolfgang Schuster
2010-09-25 15:07 ` \definenamespace and module setup (was: Info about creating modules for beginners.) Philipp Gesang
2010-09-25 17:35 ` Wolfgang Schuster
2010-09-27 8:30 ` Philipp Gesang
2010-09-23 22:08 ` Info about creating modules for beginners Steffen Wolfrum
2010-09-23 21:17 ` Aditya Mahajan
2010-09-23 21:21 ` Steffen Wolfrum
2010-09-23 20:46 ` Wolfgang Schuster
2010-09-26 0:02 ` Aditya Mahajan
2010-09-26 11:24 ` Hans Hagen
2010-09-26 15:48 ` Aditya Mahajan
2010-09-26 14:06 ` Wolfgang Schuster
2010-09-26 15:41 ` Aditya Mahajan [this message]
2010-09-26 17:51 ` Peter Münster
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=03264AD3-8D11-48B8-B51A-654A66891029@umich.edu \
--to=adityam@umich.edu \
--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).