ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Gavin via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Gavin <gavinpublic@icloud.com>
Subject: [NTG-context] Re: Metapost docs
Date: Thu, 11 Jan 2024 08:35:39 -0700	[thread overview]
Message-ID: <9E924D46-5B02-4B82-982C-1DDEE68576AF@icloud.com> (raw)
In-Reply-To: <170495290706.1644.13838152330652501096@cgl.ntg.nl>

[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]

Hi Shiv,

I am working with MetaPost in ConTeXt. Here are the resources I use, roughly in the order I search when trying to solve a problem.

- MetaFun Manual (http://www.pragma-ade.nl/general/manuals/metafun-p.pdf) This is most comprehensive and helpful source.
- MetaPost Manual (http://mirrors.ctan.org/systems/doc/metapost/mpman.pdf) This is not specific to ConTeXt, but it is very useful.
- The MetaFun page on the ConTeXt wiki (https://wiki.contextgarden.net/MetaFun_-_MetaPost_in_ConTeXt) Other pages in the wiki’s graphics area are also helpful. (https://wiki.contextgarden.net/Graphics) Searching the wiki for specific documentation on things like chemical structures is a little hit-or-miss, but often quite useful.
-The mailing list. I have the most luck with very specific questions that include a minimal working example. It should include the appropriate \starttext…\stoptext or \startMPpage…\stopMPpage, so that it can be typeset as-is.

If you want to do 3D, you may want to get Lua involved for calculations. I use

- Programming in LuaTeX page on the wiki (https://wiki.contextgarden.net/Programming_in_LuaTeX)
- Programming in Lua, 4th ed. 
by Roberto Ierusalimschy (https://www.amazon.com/gp/product/8590379868)

If you provide an example of what you hope to accomplish with MetaPost, we might have more specific recommendations. Below are two graphs that I made in TikZ, which I hope to convert to MetaPost (actually LMTX). These are from my chapter on elliptical orbits.

I hope that helps you get started.

Gavin


[-- Attachment #2: chapter07-t-b-8c929184fdcc9da93d1ffe5262fc9842.pdf --]
[-- Type: application/pdf, Size: 16995 bytes --]

[-- Attachment #3: chapter07-t-b-613fffa20a4b3581222e7b521bef3ace.pdf --]
[-- Type: application/pdf, Size: 31331 bytes --]

[-- Attachment #4: Type: text/plain, Size: 511 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-01-11 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08  0:50 [NTG-context] " Shiv Shankar Dayal
2024-01-08  9:53 ` [NTG-context] " Hans Hagen via ntg-context
2024-01-11  6:01   ` shivshankar.dayal
2024-01-11 15:35     ` Gavin via ntg-context [this message]
2024-01-11 15:54       ` Shiv Shankar Dayal
2024-01-11 16:23         ` Hans Hagen

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=9E924D46-5B02-4B82-982C-1DDEE68576AF@icloud.com \
    --to=ntg-context@ntg.nl \
    --cc=gavinpublic@icloud.com \
    /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).