ConTeXt modules

ConTeXt modules

[Giuseppe Bilotta]

Hello, this is mostly directed to Hans.

Is there a convention for the naming of modules, when creating new
ones? Since I'm quite sure not everybody is interested in the
thing I'm doing, and yet I'd like to distribute them as modules,
how should I name them?

--
Giuseppe "Oblomov" Bilotta

Re: ConTeXt modules

[Hans Hagen]

At 10:00 PM 5/29/01 +0200, Giuseppe Bilotta wrote:
>Hello, this is mostly directed to Hans.
>
>Is there a convention for the naming of modules, when creating new
>ones? Since I'm quite sure not everybody is interested in the
>thing I'm doing, and yet I'd like to distribute them as modules,
>how should I name them?

In order to prevent name clashes, the m- x- s- and p- prefixes are reserved
for myself and pragma folks. I can support u-* for user modules, but we
need to make sure that users make unique names. If needed i can put those
public user things into a separate archive. So, how about a u- prefix? 

Also, *styles* never are modules, except from those in the standard
distribution (the s- and x- ones that i make here). User styles are
environments and are loaded with \environment  

Also, when writing modules, make sure that you use existing keywords in a
consistent way, use soem Capitals in the names of macros, and use only
documented interfaces (in case of doubt: ask!). Later i will provide
scripts for normalizing files. 

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
-------------------------------------------------------------------------

Re[2]: ConTeXt modules

[Giuseppe Bilotta]

Wednesday, May 30, 2001 Hans Hagen wrote:

HH> At 10:00 PM 5/29/01 +0200, Giuseppe Bilotta wrote:
>>Hello, this is mostly directed to Hans.
>>
>>Is there a convention for the naming of modules, when creating new
>>ones? Since I'm quite sure not everybody is interested in the
>>thing I'm doing, and yet I'd like to distribute them as modules,
>>how should I name them?

HH> In order to prevent name clashes, the m- x- s- and p- prefixes are reserved
HH> for myself and pragma folks. I can support u-* for user modules, but we
HH> need to make sure that users make unique names. If needed i can put those
HH> public user things into a separate archive. So, how about a u- prefix? 

Sounds sensible to me. I just wanted to submit the "speech"
module, unless you plan to "stream-line" it in the core
distribution (btw, I finally have it working properly, so if you
want the final version, I can post it, here or privately).

HH> Also, *styles* never are modules, except from those in the standard
HH> distribution (the s- and x- ones that i make here). User styles are
HH> environments and are loaded with \environment  

Yes. Also please see my other post about the
environment/product/component stuff.

--
Giuseppe "Oblomov" Bilotta