ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: James Fisher <jameshfisher@gmail.com>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Occasional words sticking out from flush-right
Date: Wed, 3 Mar 2010 23:19:17 +0000	[thread overview]
Message-ID: <771da05a1003031519w7803d7dcn9cb4c52be548ffec@mail.gmail.com> (raw)
In-Reply-To: <20100303215354.GB2029@phare.normalesup.org>


[-- Attachment #1.1: Type: text/plain, Size: 2468 bytes --]

Well, it's reassuring that people can at least admit this is a closed
community.  (But aren't churches meant to evangelize?)

----
"For using ConTEXt, no TEX-- programming skills and no technical background
are needed." (http://wiki.contextgarden.net/What_is_ConTeXt)
"So why don't you grep in base/* ?" (Luigi; I appreciate the advice but a
bit of a contradiction methinks)
----

Also, re "there is only one  ConTeXt developer --- Hans Hagen":
I'd suggest a few reasons for this are:
(1) in order to develop on a project, you first need a the high-level
appreciation of the system that comes from documentation
(2) ConTeXt does not have any revision control system that I can see (the
only source code browser seem to be http://source.contextgarden.net/ which
looks entirely custom); all I can find is the SVN of the in-progress manual
(3) The low-level macro documentation at
http://texshow.contextgarden.net/is a start, but: (i) instead of a
custom system with basic editing, a modern
documentation system (I'm thinking of http://sphinx.pocoo.org/ used for the
*fantastic* documentation of the Python library) would be more productive,
and (ii) this documentation is completely non-structured, being just an
alphabetical list.

(This from the community that came up with "literate programming"?)

Also, just having one developer is not at all anything to celebrate, and no,
this model of development is not OK.  I wouldn't say it's a model for
development at all.  Other projects manage just fine without naming
conflicts. Admittedly this is with the amazingly obvious concept of
namespacing, which TeX doesn't have -- though I've just been reading an
article <http://www.tug.org/TUGboat/Articles/tb27-0/neugebauer.pdf> on
namespacing in <http://www.extex.org/>.


James

On Wed, Mar 3, 2010 at 9:53 PM, Arthur Reutenauer <
arthur.reutenauer@normalesup.org> wrote:

> > (Arthur, what about your church of TeX?)
>
>   I deny everything.
>
>        Arthur
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 3682 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
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:[~2010-03-03 23:19 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.607.1267648881.26807.ntg-context@ntg.nl>
2010-03-03 21:47 ` Vyatcheslav Yatskovsky
2010-03-03 21:53   ` Arthur Reutenauer
2010-03-03 23:19     ` James Fisher [this message]
2010-03-04  0:08       ` Aditya Mahajan
2010-03-04  2:35         ` James Fisher
2010-03-04  4:06           ` Aditya Mahajan
2010-03-04 14:39             ` James Fisher
2010-03-04 17:11               ` Aditya Mahajan
2010-03-04 17:15                 ` luigi scarso
2010-03-04 17:30                   ` Aditya Mahajan
2010-03-04 18:43                     ` luigi scarso
2010-03-04 17:50                 ` James Fisher
2010-03-04  7:10           ` luigi scarso
2010-03-04 14:25             ` James Fisher
2010-03-04 18:42               ` luigi scarso
2010-03-04 19:44                 ` James Fisher
2010-03-04 20:04                   ` Aditya Mahajan
2010-03-04 20:47                   ` luigi scarso
2010-03-04 23:31                     ` James Fisher
2010-03-04 23:36                       ` Aditya Mahajan
2010-03-04 23:47                         ` James Fisher
2010-03-05  9:30                   ` luigi scarso
2010-03-03 23:09 ` setbreakpoints Vyatcheslav Yatskovsky
2010-03-04 14:40   ` setbreakpoints James Fisher
2010-03-03 19:19 Occasional words sticking out from flush-right James Fisher
2010-03-03 19:36 ` Wolfgang Schuster
2010-03-03 20:41   ` James Fisher
2010-03-03 20:44     ` luigi scarso
2010-03-03 21:19       ` James Fisher
2010-03-03 22:46         ` luigi scarso

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=771da05a1003031519w7803d7dcn9cb4c52be548ffec@mail.gmail.com \
    --to=jameshfisher@gmail.com \
    --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).