9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Sigrid Solveig Haflínudóttir" <sigrid@ftrv.se>
To: 9front@9front.org
Subject: Re: [9front] graphics tools
Date: Tue, 27 Sep 2022 17:59:32 +0200	[thread overview]
Message-ID: <285A06EA6B6136FC135D0C69E75AFCAF@ftrv.se> (raw)
In-Reply-To: <YzMaP2UAE5k/yOPr@wopr>

Quoth Kurt H Maier <khm@sciops.net>:
> On Tue, Sep 27, 2022 at 10:56:50PM +1300, umbraticus@prosimetrum.com wrote:
> > > https://git.sr.ht/~raingloom/postscript-sketches
> > 
> > Thanks for the pointers. Fun stuff; here's a quick one:
> > 
> > http://runjimmyrunrunyoufuckerrun.com/demo/pspjw
> > 
> > Make sure to sysupdate first to get the latest togif fix (thanks sigrid!)
> > or just feast your eyes on the result:
> > http://runjimmyrunrunyoufuckerrun.com/demo/pspjw.gif
> > 
> > I know there is an ongoing effort to get a native pdf renderer going
> > but ps seems quite entwined in the system and kinda enjoyable in
> > its own right, so I wonder whether that will indeed put an end to
> > our crusty old gs...
> > 
> > umbraticus
> 
> If I had Infrastructure Money, an API-compatible ghostscript replacement
> would be a boon to the whole world.  Shame the folks who haunt bug
> trackers demanding things be rewritten in their language du jour are
> focused on overthrowing the tyranny of ls(1) than doing something
> genuinely productive.
> 
> khm

Maybe not API-compatible, but pdffs-adjacent folks (me too) were
looking at https://github.com/luser-dr00g/xpost as a possible base for
future work in ghostscript replacement effort in 9front.

As usual, a lot code has to be written and main resource for that is
time.


  reply	other threads:[~2022-09-27 16:00 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  0:58 william
2022-09-23  1:06 ` ori
2022-09-23  1:15   ` william
2022-09-23  2:04     ` ori
2022-09-23  2:12       ` william
2022-09-23  2:24         ` Stanley Lieber
2022-09-23  2:38           ` william
2022-09-23  2:44             ` Stanley Lieber
2022-09-23  4:21               ` umbraticus
2022-09-23  6:55                 ` Steve Simon
2022-09-23  7:15                 ` kvik
2022-09-23 21:16               ` william
2022-09-23 21:16               ` william
2022-09-23 21:53                 ` Stanley Lieber
2022-09-23 22:02                   ` william
2022-09-23 22:35                     ` Stanley Lieber
2022-09-25  1:57                     ` sl
2022-09-25  2:37                       ` william
2022-11-25 21:37         ` noam
2022-11-26  1:15           ` umbraticus
2022-11-27 20:46             ` umbraticus
2022-09-23  1:15   ` william
2022-09-23 20:45   ` Stuart Morrow
2022-09-23 10:54 ` tlaronde
2022-09-23 18:17 ` Csepp
2022-09-23 22:33   ` umbraticus
2022-09-24 18:29     ` Csepp
2022-09-27  9:56       ` umbraticus
2022-09-27 15:43         ` Kurt H Maier
2022-09-27 15:59           ` Sigrid Solveig Haflínudóttir [this message]
2022-09-28  9:39             ` tlaronde
2022-09-30  6:39               ` william
2022-09-30  6:39               ` william

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=285A06EA6B6136FC135D0C69E75AFCAF@ftrv.se \
    --to=sigrid@ftrv.se \
    --cc=9front@9front.org \
    /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).