From: Patrick Gundlach <patrick@gundla.ch>
Subject: Re: What about dynamic documentation?
Date: Sat, 17 Dec 2005 00:12:30 +0100 [thread overview]
Message-ID: <m2k6e4ljq9.fsf@levana.de> (raw)
In-Reply-To: <43A31BE2.3010207@elvenkind.com> (Taco Hoekwater's message of "Fri, 16 Dec 2005 20:56:18 +0100")
Hi Taco and Jérôme,
>> However, this seems rather far from the pdf manuals and does not
>> really help a newbie as I am.
>
> Definately it could be improved. In IT, almost everything is
> suboptimal starting the second after it's birth.
And it was the starting point of contextgarden (and my first web-app).
> Perhaps we should continue this discussion on the developers list,
> dev-context@ntg.nl?
>
> It is likely we will spend some other mails on this subject,
> and perhaps it is better not to clutter the general list. Anybody
> willing to discuss/help out can easily subscribe to that list
> (even if just for a while). Is that OK?
Good, but let me add a general remark first also on this list.
[...]
> It could also easily be backported to the XML data. Patrick?
yes. put that one on the todo list.
> Perhaps the examples could be fed through the Live ConTeXt, just like
> the wiki examples?
already on the todo list...
As my two answers imply, I already have a long todo list for texshow.
(I even have two translation updates from Mojca that I haven't
implemented yet - sorry). I hope that I will have some time between
Christmas and new year for texshow 2. Perhaps we should follow Taco's
suggestion to discuss more technical details on the underlying xml
description on the dev' list.
Patrick
--
ConTeXt wiki and more: http://contextgarden.net
prev parent reply other threads:[~2005-12-16 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 13:19 Jérôme Laurens
2005-12-06 13:59 ` Taco Hoekwater
2005-12-06 14:26 ` Adam Lindsay
2005-12-16 7:31 ` Jérôme Laurens
2005-12-16 19:56 ` Taco Hoekwater
2005-12-16 23:12 ` Patrick Gundlach [this message]
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=m2k6e4ljq9.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).