ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec1@email.si>
Subject: Re: Re: new stuff for brave users
Date: Wed, 04 Aug 2004 12:13:50 +0200	[thread overview]
Message-ID: <4110B6DE.8020605@email.si> (raw)
In-Reply-To: <m2pt67gsgf.fsf@levana.de>


>>http://live.contextgarden.net
> 
> one thing to add: I'd appreciate any kind of comments, since I have
> only tested it with safari and old versions of mozilla. If you think
> that there is anything strange, don't hesitate to tell me! And don't
> rely on your impression that others will do so, so there would no
> need for feedback. 
> 
> Patrick

Here is what I wrote yesterday, but haven't sent yet :)
Did I send this accidentaly ? :) :) :)

It's a great service, it would just make sense to connect the wiki and 
code rendering, so that the code written would be automatically 
"copy-pasted" in the window (or any other mechanism to enable quick 
acces to the documents described in wiki).

Well done again,
	Mojca Miklavec

***   ***   ***   ***   ***

1.) WIKI

1.1.) It would make sense to add a link to CenTeXt wiki from
www.pragma-ade.com

1.2.) http://www.mayer.dial.pipex.com/latexrender.zip
is an example of a tool which (as long as I have seen and understood it
correctly) does nothing else but wrapping a (LaTeX) code, executing it
and cropping the relevant part into PNG image. There are already modules
for PHPBB and wiki. I guess it wouldn't take so much additional effort
to enable some excelent feature to both the ConTeXt and texshow wiki:
* rendering image as an example of the effect of the code written there

For example, if someone would write:
    [context]
    a couple of lines of context code
    [/context]

it would be shown as the code as well as a PNG image showing the result
and perhaps an additional link to the PDF document rendered.

  parent reply	other threads:[~2004-08-04 10:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04  9:01 Patrick Gundlach
2004-08-04  9:31 ` Patrick Gundlach
2004-08-04  9:55   ` Vit Zyka
2004-08-04 10:03     ` Patrick Gundlach
2004-08-04 10:42       ` Vit Zyka
2004-08-04 10:06     ` Hans Hagen
2004-08-04 10:12     ` Taco Hoekwater
2004-08-04 10:21       ` texshow-web Patrick Gundlach
2004-08-04 10:57       ` Re: new stuff for brave users Hans Hagen
2004-08-04 11:06         ` Patrick Gundlach
2004-08-04 10:13   ` Mojca Miklavec [this message]
2004-08-04 11:17     ` Patrick Gundlach
2004-09-10  9:16     ` Patrick Gundlach
2004-08-04 11:34 ` Floris van Manen
2004-08-04 12:24   ` Tobias Burnus
2004-08-26  9:43     ` Patrick Gundlach
2004-08-04 14:22 ishamid
2004-08-04 22:51 ` Hans Hagen Outside
2004-08-05  1:39   ` Brooks Moses
2004-08-05  8:58     ` Henning Hraban Ramm

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=4110B6DE.8020605@email.si \
    --to=mojca.miklavec1@email.si \
    --cc=mojca.miklavec@guest.arnes.si \
    --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).