ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: MF <massifr@fastwebnet.it>
To: ntg-context@ntg.nl
Subject: Re: roadmap
Date: Tue, 15 May 2018 11:01:02 +0200	[thread overview]
Message-ID: <322d89dec92cb67aea6dab8f8fd25d96a2479f9b.camel@fastwebnet.it> (raw)
In-Reply-To: <c504ea08-a021-4444-4eba-c2894d72da52@xs4all.nl>


> > * References: see Massimiliano’s question, apparently there are
> > options missing for code before/after the list of pages
> 
> These hooks were added; adding a few more hooks is normally no big
> deal 
> ... the main problem with such additions is that they seldom get 
> documented (in fact that imo is also a it up to the one requesting
> such 
> features).
> 

Touché! I've added them to the wiki.

I was already updating that page of the wiki (\setupregister) on
Friday, but also realized that it was way behind the syntax you can
check with setup-en.pdf (the Commands manual).
It missed the brand new "pageleft" and "pageright" parameters, but even
much more than them. So i asked myself about the opportunity to
document a brand new feature without the missing ones that have been
already in place for a much longer time.
Anyway, that's the spirit of a wiki: everybody can add his 2 cents of
knowledge.

The table of the command parameters was also difficult to read and
modify in the wiki source, so i gave up for that moment and wondered
about a more general solution for command documentation.
Your messages today motivated me to update that page anyway.

The setup-en.pdf manual is a great source of documentation and it's
synchronized with every new version, because it's automatically
generated from sources.

It lets you know the commands, their parameters and their types.
I've looked a bit into the "i-" files in the "interface" directory of
the ConTeXt distribution, and i've seen that the commands are also
classified into categories.

What you miss in that manual is the parameters' meaning and some
example of usage.
I'm thinking about some companion files to the "i-" ones that carry the
information about the parameters' meaning and usage.
Some of those texts could be "recycled" from the current wiki pages.
Then we could generate some automatic, up to date wiki pages directly
from the combination of those files.

I'm not going to work on that before the meeting and i've already
promised more than i can achieve.
But we could discuss that at the meeting.

Greetings,
Massi
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2018-05-15  9:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 15:17 roadmap Hans Hagen
2018-05-14 19:36 ` roadmap Henning Hraban Ramm
2018-05-14 21:26   ` roadmap Hans Hagen
2018-05-15  9:01     ` MF [this message]
2018-05-14 22:52 ` roadmap Henri Menke
2018-05-14 23:34   ` roadmap Hans Hagen
2018-05-16  5:38     ` roadmap Henri Menke
2018-05-16  6:24       ` roadmap Joseph Canedo
2018-05-16  7:28       ` roadmap Hans Hagen
2018-05-14 23:41   ` roadmap luigi scarso
2018-05-15 19:17 ` roadmap Pablo Rodriguez
2018-05-15 21:26   ` roadmap Hans Hagen
2018-05-16 15:18     ` roadmap Pablo Rodriguez
2018-05-16 19:14 ` roadmap Fabrice L
2018-05-17 13:06   ` roadmap Hans Hagen
2018-05-17 14:24     ` roadmap Mohammad Hossein Bateni
2018-05-17 15:47       ` roadmap Otared Kavian
2018-05-17 16:50         ` roadmap Hans Hagen
2018-05-15  6:15 roadmap Christoph Reller
2018-05-15  6:23 ` roadmap luigi scarso
2018-05-15  6:36 ` roadmap Hans Hagen
2018-05-15 14:46 roadmap Christoph Reller
2018-05-15 14:51 ` roadmap luigi scarso
2018-05-18  9:54 roadmap Christoph Reller

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=322d89dec92cb67aea6dab8f8fd25d96a2479f9b.camel@fastwebnet.it \
    --to=massifr@fastwebnet.it \
    --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).