From: Joshua Branson <jbranso@fastmail.com>
To: <guile-user@gnu.org>
Subject: Re: How to get started in guile & programming generally
Date: Wed, 29 Aug 2018 17:21:11 -0400 [thread overview]
Message-ID: <8736uwc1iw.fsf@fastmail.com> (raw)
In-Reply-To: <CAJ=RwfabptRxpFUsK0qimW2b+MTPLrL1p6fxGHLbEDgrFhFT9w@mail.gmail.com> (David Thompson's message of "Mon, 27 Aug 2018 09:30:42 -0400")
"Thompson, David" <dthompson2@worcester.edu> writes:
> On Sun, Aug 26, 2018 at 3:12 PM, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
>>
>>> I've heard about chickadee! I've tried to install it before, but I
>>> haven't been successful yet. Perhaps I'll have to try again.
>>
>> What's the issue? Please post a backtrace.
>> I can chickadee flawlessly here, maybe I can help.
>
> I can also try to help. I should make a new release with all the
> latest code, maybe the experience will be better since some things
> were tweaked that were causing problems on certain computers. (There's
> API breakage, though, be warned!)
>
>> And by the way, chickadee is an awesome piece of software: it is such a
>> refreshing video game programming experience.
>
> That's good to hear! BTW, I am currently working on a small game
> engine built on top of Chickadee. My intent with Chickadee was to
> give people all of the building blocks to make games with Guile, but
> without strapping them to an opinionated engine. So, Starling is going
> to be one of those opinionated engines! The core abstractions are
> inspired by Godot and Python's Cocos2D which I used many years ago;
> it's 2D only for the time being; it uses GOOPS heavily (this may or
> may not sound good to you!); and it has a built-in developer mode that
> provides a REPL server, game loop error debugger, and live asset
> reloading (for images, sounds, all that non-code stuff). Stay tuned!
+1
>
> - Dave
next prev parent reply other threads:[~2018-08-29 21:21 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 [this message]
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
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=8736uwc1iw.fsf@fastmail.com \
--to=jbranso@fastmail.com \
--cc=guile-user@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).