Hi all!

On 2010-09-25 <19:35:31>, Wolfgang Schuster wrote:
> 
> Am 25.09.2010 um 17:07 schrieb Philipp Gesang:
> 
> > Could you please explain what these other parameters do:
> >  style=yes,
> >  parent=fb
> > Also, what other values would the parameter ‘setup’ accept
> > besides ‘list’?
> 
> I’ll come back to this later.

Thanks in advance! For now there’s question marks galore on the
wiki page.

> +-----------+------------+--------------+-------------+
> | Namespace | Name       | File         | Description |
> +-----------+-----------------------------------------+
> | fb        | fancybreak | t-fancybreak | …           |
> +-----------+------------+--------------+-------------+
> | …         | …          | …            | …           |

Hmm, i was thinking with a proper hyperlink the description would
be superfluous. But as there’s plenty of horizontal space in the
table that is not a problem. (After all, it’s not wikipedia; can’t
hurt to have some real information.)

I think it has to be up to the maintainer of module to register
it on the wiki. If the module is orphaned, a regular user should
be fine as well.

The wiki page is written with mkiv in mind only. Now, should the
module list extend to mkii style modules as well or should we
wait for the modules to be adapted by the maintainers? An extra
column indicating the version could do as well.


Regards, Philipp

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

Attachment: pgppWTM1l9Eb1.pgp
Description: PGP signature

___________________________________________________________________________________
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 via email to