ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jonas Baggett <jonasb@tranquille.ch>
To: ntg-context@ntg.nl
Subject: Re: Ideas for improving documentation of ConTeXt
Date: Mon, 10 Oct 2016 00:49:49 +0200	[thread overview]
Message-ID: <48a788bc-3872-4a95-ec24-1999d7300c06@tranquille.ch> (raw)
In-Reply-To: <e7b6ec97-146f-f1ee-75c4-aef9d9c41d72@gmail.com>

Hello Henri,

Le 09. 10. 16 à 21:31, Henri Menke a écrit :
> please don't be disappointed but you are not the first person to suggest such a thing.  You may now ask, why doesn't such a thing exist then?  Well, the basic answer is, go ahead and implement it.
I won't go ahead and implement it if I am the only one who would think 
it is a good idea. That's why I asked for some feedback. It happens 
sometimes that I could have an idea that looks great in my eyes, but 
then seems a little less shiny after hearing some feedback. But since I 
wasn't the first person to suggest such a thing, It seems to me that my 
idea goes in the right direction, isn't it ? It doesn't mean that no 
improvement is needed, and it still need to be implemented.

> Most probably no one else will volunteer to do it and especially the people from PRAGMA surely have better things to do. They merely develop and use ConTeXt (...)
Here I don't agree. People from PRAGMA are probably better at 
developping ConTeXt than starting in parallel a new project like that, 
but it doesn't mean that this idea is necessarly not worth considering. 
I wasn't either suggesting that they should be the people who start 
implementing the idea.
> (...) and were so kind as to provide us a huge bunch of documentation already (http://pragma-ade.nl/document-1.htm).
Yes I just saw that you are right about the documentation, they have 
already made a huge work on that. I was maybe too quick about my 
conclusion, I am sorry if I did offend those who have already make all 
that work. I was actually doing a cover letter in ConTeXt and since I 
wasn't able to find uptodate informations about some of the commands I 
was a little frustrated. But yes the letter module is third party and I 
just saw in the wiki that it is said to be still in developpment, so 
interface changes are to be expected and not necessarly all documented. 
Since I am new to ConTeXt, my views on ConTeXt documentation got biased. 
But now I am pretty happy with the results I have with my document, so 
most of the troubles are behind, I guess :-).

On the other hand, some of the documentation still need to be updated. 
Since ConTeXt is quick to evolue, having uptodate documentation would be 
a huge task and I also understand that it may not be the most 
interesting part for developpers ;-). My proposition was about to 
mitigate that problem with making accessible examples with some advanced 
search to quickly find relevant results.

Maybe someday ConTeXt will be more mature and have a more stable 
interface, then it would be easier to have uptodate documentation. But 
it is only the analysis of someone who is only starting to know ConTeXt, 
so I won't assume to be totally correct.

Cheers,
Jonas
___________________________________________________________________________________
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	other threads:[~2016-10-09 22:49 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-09 11:18 Jonas Baggett
2016-10-09 13:49 ` Yi Qingliang
2016-10-10  5:21   ` Jonas Baggett
2016-10-09 19:31 ` Henri Menke
2016-10-09 22:49   ` Jonas Baggett [this message]
2016-10-10  7:35     ` Hans Hagen
2016-10-11 21:36       ` Jonas Baggett
2016-10-09 20:51 ` Wolfgang Schuster
2016-10-10  5:43   ` Jonas Baggett
2016-10-10  7:24     ` Hans Hagen
2016-10-11 21:05       ` Jonas Baggett
2016-10-12 11:30       ` Jonas Baggett
2016-10-12 15:29         ` Yi Qingliang
2016-10-12 15:33           ` Mica Semrick
2016-10-12 17:32             ` Jonas Baggett
2016-10-12 17:45               ` Bomber K.
2016-10-12 17:55           ` Bomber K.
2016-10-10  7:57     ` Thomas A. Schmitz
2016-10-10 17:04       ` Jean-Pierre Delange
2016-10-10 17:34         ` Hans Hagen
2016-10-10 21:41         ` Henning Hraban Ramm
2016-10-11  5:20           ` Jean-Pierre Delange
2016-10-12 21:18         ` Jonas Baggett
2016-10-12 10:17       ` Jonas Baggett
2016-10-10  5:32 ` Aditya Mahajan
2016-10-10  5:43   ` Aditya Mahajan
2016-10-11 20:26     ` Jonas Baggett
2016-10-11 20:40       ` Henning Hraban Ramm
2016-10-12 21:27         ` Jonas Baggett
2016-10-13  8:15           ` Henning Hraban Ramm
2016-10-13  9:23             ` Aditya Mahajan

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=48a788bc-3872-4a95-ec24-1999d7300c06@tranquille.ch \
    --to=jonasb@tranquille.ch \
    --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).