ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Patrick Gundlach" <patrick@gundla.ch>
Subject: Re: Best source of ConTeXt documentation?
Date: 2 Aug 2004 17:46:38 +0200	[thread overview]
Message-ID: <m24qnl4k69.fsf@levana.de> (raw)
In-Reply-To: <200408021457.i72Ev94B025117@blue1.Math.Berkeley.EDU> (Paulo Ney de Souza's message of "Mon, 2 Aug 2004 07:57:09 -0700 (PDT)")

Hello, 

> This is one of the sore points of ConTeXt and of the development
> effort. People at Pragma are willing to show off but not willing
> to share code and teach by example... contrary to most opensource
> projects I have seen.

Oh come on, this is completely crap. The people at PRAGMA (i.e. Hans)
share ConTeXt, wich is the holy grail that PRAGMA is based on
(besides the knowledge). It is such a generous gift to the community.
Please think about if you write stuff like that.

You are right, that not all (only few) manuals are available in .tex
format. See pdftex manual and the magazines. Putting source
code online needs time, a lot of time. Source code needs to get
documented. And I don't know Hans very well, but I'd guess that his
day only has 24h.

There are already some styles in the ConTeXt wiki. And there are
styles that come with the distribution. 

> Maybe it is time for us to start an group to reverse-engineer some
> of these files and post them into a public archive.

Why reverse-engineer? Just cook up the style you want. If you have
questions doing this, ask on the ConTeXt list. If you are ready, put
the style onto the Wiki. The styles at pragma are very good, but
definitely not the only way to go. Making a good style is not
copy/paste. It is a matter of experience. Experience is something you
have to gain yourself.

And yes, it is time for us to put examples online. But the ConTeXt
community is still rather small. So there won't be many results in a
short time.


Paulo,

You can do the first step. Go to the wiki, edit a page that states
your questions regarding style development. Put a table of contents
or something similar there, which steps you would like to see, which
things you would like to have explained and so on. After that "we"
(the more experienced ConTeXt users) can fill in the gaps. And
finally we all have a small manual on style design. This is much
better than being so aggressive on the unwillingness to share source.


Patrick

(btw: looking for some beta testers for a new service)

-- 
ConTeXt wiki: http://contextgarden.net
texshow-web:  http://texshow.contextgarden.net
List archive: http://archive.contextgarden.net

  reply	other threads:[~2004-08-02 15:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 14:57 Paulo Ney de Souza
2004-08-02 15:46 ` Patrick Gundlach [this message]
2004-08-02 23:13   ` Paulo Ney de Souza
2004-08-03  6:31     ` Patrick Gundlach
2004-08-02 16:08 ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2004-08-03 15:13 Paulo Ney de Souza
2004-08-03 17:44 ` Patrick Gundlach
2004-08-03  5:05 Paulo Ney de Souza
2004-08-03  6:40 ` Patrick Gundlach
2004-08-03  9:56 ` Nikolai Weibull
2004-08-03  3:05 skhilji
2004-08-03  6:38 ` Patrick Gundlach
2004-08-03  7:09 ` Hans Hagen
2004-08-02 19:30 Paulo Ney de Souza
2004-08-02  2:55 skhilji
2004-08-01 22:23 Brooks Moses
2004-08-02  1:57 ` Gary Pajer

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=m24qnl4k69.fsf@levana.de \
    --to=patrick@gundla.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).