unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: How to get started in guile & programming generally
Date: Fri, 31 Aug 2018 11:04:39 -0400	[thread overview]
Message-ID: <CAJ=RwfY+CueHAUpr5cVaBOkbYQ67tGkd23duE1bqzGDaYCkeXw@mail.gmail.com> (raw)
In-Reply-To: <87in3qojos.fsf@gnu.org>

Hi Jan,

On Fri, Aug 31, 2018 at 7:32 AM, Jan Nieuwenhuizen <janneke@gnu.org> wrote:
> Pierre Neidhardt writes:
>
>> And by the way, chickadee is an awesome piece of software: it is such a
>> refreshing video game programming experience.
>
> I've been looking at chickadee and wondering if how to use that for a
> learn to program experience for childrden.
>
> Do you know of real simple hello-world style "games" made with
> chickadee, say just the bird moving from left to right, respond to arrow
> press or space bar?

I don't know of anyone that has done that. It's not hard to do, but I
think using something higher level built on Chickadee would be more
appropriate for teaching children.  Chickadee is high-level in a sense
because it abstracts away complicated OpenGL things and provides
useful utilities, but low-level in another sense that it leaves it up
to the user to assemble all the pieces.  "Batteries not included", if
you will.  I'm working on a project called Starling, which is a small
object-oriented game engine that has the batteries included.  I'll
share more when I'm ready for a 0.1 release.

- Dave



  reply	other threads:[~2018-08-31 15:04 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-25 17:16 How to get started in guile & programming generally Joshua Branson
2018-08-25 19:01 ` Amirouche Boubekki
2018-08-25 20:10   ` Pierre Neidhardt
2018-08-25 20:35     ` Matt Wette
2018-08-27 12:39     ` Ludovic Courtès
2018-08-27 13:15       ` Thompson, David
2018-08-26 18:16   ` Joshua Branson
2018-08-26 19:12     ` Pierre Neidhardt
2018-08-27 13:30       ` Thompson, David
2018-08-27 20:42         ` Arne Babenhauserheide
2018-08-29 21:21         ` Joshua Branson
2018-08-29 21:20       ` Joshua Branson
2018-08-29 21:27         ` Amirouche Boubekki
2018-08-30 13:11           ` Joshua Branson
2018-08-30 15:45             ` Amirouche Boubekki
2018-09-03 20:53           ` Joshua Branson
2018-10-19 17:02             ` Joshua Branson
2018-08-30 19:09         ` Arne Babenhauserheide
2018-08-31 11:32       ` Jan Nieuwenhuizen
2018-08-31 15:04         ` Thompson, David [this message]
2018-08-31 16:49           ` Jan Nieuwenhuizen
2018-08-31 23:04             ` Ludovic Courtès
2018-08-31 17:45         ` Amirouche Boubekki
2018-08-27 18:46     ` Amirouche Boubekki
2018-08-27 19:08       ` John Cowan
2018-08-29 21:33       ` Joshua Branson
2018-08-30 21:42         ` Arne Babenhauserheide
2018-08-31  8:07           ` tomas
2018-08-31 14:44             ` Joshua Branson
2018-09-01 10:00             ` Arne Babenhauserheide
2018-09-01 10:49               ` tomas
2018-09-02 23:09                 ` Arne Babenhauserheide
2018-08-31 14:42           ` Joshua Branson
2018-08-27 20:54     ` Arne Babenhauserheide
2018-08-29 21:35       ` Joshua Branson
2018-08-30 20:19         ` Arne Babenhauserheide
2018-08-31 14:41           ` Joshua Branson
2018-09-01 10:01             ` Arne Babenhauserheide
2018-09-01 16:26               ` Joshua Branson

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ=RwfY+CueHAUpr5cVaBOkbYQ67tGkd23duE1bqzGDaYCkeXw@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=guile-user@gnu.org \
    --cc=janneke@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).