From: "Sudarshan S Chawathe" <chaw@eip10.org>
To: Per Bothner <per@bothner.com>
Cc: kawa <kawa@sourceware.org>
Subject: Re: (kawa pictures) square-limit pictures
Date: Sun, 30 Oct 2016 18:54:00 -0000 [thread overview]
Message-ID: <9603.1477853671@vereq.eip10.org> (raw)
In-Reply-To: Your message of "Sun, 30 Oct 2016 09:39:11 -0700." <57446255-4576-aa45-5657-6c001daff9b7@bothner.com>
> From: Per Bothner <per@bothner.com>
> Date: Sun, 30 Oct 2016 09:39:11 -0700
> Neat. What do you think of the idea of taking the SICP functions and
> moving them into a new library? Perhaps named (kawa pictures sicp) ?
> Or maybe just (sicp pictures) ? Racket uses (require sicp-pict)
I think it's a great idea.
An issue related (I think) to the choice of names is how closely the
library follows the original SICP pictures language v. how closely it
tries to match Kawa's composable pictures style. Here I am thinking
about, for instance, the implementation of "below" using SICP's explicit
notion of painting into frames (and frame transformations) v. using
Kawa's re-center and vbox. When I first started writing the
square-limit example, I went with the first option, but then decided
that is probably not in the spirit of the Kawa pictures library. There
is probably value in having both methods.
I will take a look at how the Racket library does things.
Regards,
-chaw
next prev parent reply other threads:[~2016-10-30 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 15:56 Sudarshan S Chawathe
2016-10-30 16:39 ` Per Bothner
2016-10-30 18:54 ` Sudarshan S Chawathe [this message]
2016-10-30 19:10 ` Per Bothner
2016-10-31 22:11 ` Sudarshan S Chawathe
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=9603.1477853671@vereq.eip10.org \
--to=chaw@eip10.org \
--cc=kawa@sourceware.org \
--cc=per@bothner.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 read-only IMAP folder(s) and NNTP newsgroup(s).