From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Vector Brushes for MetaFun?
Date: Wed, 1 Sep 2021 12:48:06 +0200 [thread overview]
Message-ID: <190845A1-FAC2-4C8C-8737-F966916B2CE1@fiee.net> (raw)
Hi, since Jacob started the pony mode, here’s one I’d like to ride:
MetaPost pens are constant, i.e. they never change over the length of a path.
Commercial vector graphics apps have “vector brushes”, e.g. Adobe Fresco:
https://helpx.adobe.com/fresco/using/vector-brushes.html
The page nicely shows the necessary variables.
In Inkscape you can combine “brush images” like
https://publicdomainvectors.org/en/free-clipart/Paintbrushes-for-Inkscape/86586.html
with pen shapes:
https://logosbynick.com/custom-brushes-in-inkscape/
This stretches the whole shape over the path – not perfect but good enough (and the same what e.g. “my” Affinity Designer does).
(https://affinity.serif.com/designer/)
Is this possible with MetaFun, i.e. use a closed path and distort/stretch it along an open path?
If, how?
Hraban
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2021-09-01 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 10:48 Henning Hraban Ramm via ntg-context [this message]
2021-09-01 12:06 ` Hans Hagen via ntg-context
2021-09-01 12:52 ` Henning Hraban Ramm via ntg-context
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=190845A1-FAC2-4C8C-8737-F966916B2CE1@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).