From: "Rodrigo G. López" <rgl@antares-labs.eu>
To: 9front@9front.org
Subject: Re: [9front] 9front pico
Date: Sun, 20 Jan 2019 18:08:07 +0000 [thread overview]
Message-ID: <2233B93E-AA8B-4929-8E95-7CA9C79D4276@antares-labs.eu> (raw)
In-Reply-To: <1AF469D179A8A46C580EF18E13F389BE@wopr.sciops.net>
thank you for this, qwx!
On January 20, 2019 4:42:25 PM UTC, qwx <qwx@sciops.net> wrote:
>Hello,
>
>In case anyone is interested, I've extended rsc's pico with a couple of
>new
>features.
>
>Changes:
>- remove p9p shit and some bitrot
>- use mk to build binary instead of hardcoding CC/LD
>- arbitrary image sizes; set when loading or displaying an image;
>default
> 248x248
>- work on ABGR32 images; channels are accessed via a third 'z'
>coordinate
>- add &&, || operators
>- name nameless images as $1, $2,...
>
>Note: some of the choices I've made are questionable.
>
>This version is available in my contrib under pico/.
>
>Cheers,
>
>qwx
-rodri
prev parent reply other threads:[~2019-01-20 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 16:42 qwx
2019-01-20 18:08 ` Rodrigo G. López [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=2233B93E-AA8B-4929-8E95-7CA9C79D4276@antares-labs.eu \
--to=rgl@antares-labs.eu \
--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).