From: Amirouche Boubekki <amirouche@hypermove.net>
To: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>
Cc: ludo@gnu.org,
guile-devel-bounces+amirouche+dev=hypermove.net@gnu.org,
guile-devel <guile-devel@gnu.org>
Subject: Re: New logo and website design proposal
Date: Mon, 12 Oct 2015 22:32:32 +0200 [thread overview]
Message-ID: <46c812a04f6d49b7ed851689abd23fcb@hypermove.net> (raw)
In-Reply-To: <4c4d2e0e9237e789a0aabb32d048d6b4@openmailbox.org>
Le 2015-10-12 20:15, Luis Felipe López Acevedo a écrit :
> On 2015-10-12 08:26, ludo@gnu.org wrote:
>> Aleix Conchillo Flaqué <aconchillo@gmail.com> skribis:
>>
>>> I have a suggestion: would it be possible to show only one code
>>> sample in
>>> the Code examples section? The code sample would periodically switch
>>> to a
>>> new one smoothly and also the user should be able to jump from sample
>>> to
>>> sample by clicking some arrows. Something like racket-lang (but much
>>> nicer
>>> with your design!). Also, it would save some space. The code could be
>>> on
>>> the left and the explanation on the right side with the title on top
>>> of the
>>> explanation.
>>
>> I agree that it would be nice, if possible.
>>
>> OTOH the current web site has the advantage of being JavaScript-free.
>>
>> WDYT, Felipe?
>>
>
> I'm fine with Aleix suggestion. And it can be done so that the
> examples are shown in a descent way without the effects for people who
> don't use JavaScript. But I'd pass on the implementation because I
> don't like much using JavaScript :)
I can do it, if nobody shims in... When I am finished with the tutorial.
Any comment is welcome.
First I tried to follow hylang tutorial [0], but I found it too short. I
really like clojure koans [1], but there is not guilescript. I did not
do much research, in particular there might be interesting stuff to use
in "how to design programs" [2].
So I settled on 4 parts tutorial split into sections, but not deeper,
where the first paragraph introduce a concept and the second paragraph
apply the concept in the general context of guilers doing a hackfest. I
did not talk about macros, I will think about a way to spread the
different macros in all the parts.
Here is the plan:
# Learn Scheme Guile
## Getting started [3]
The main illustration is a breakfast box.
- call procedure
- define a variable
- how to create list
- how to create pairs
- how to create scheme dictionary aka. assoc
- how to define a procedure
- how to to create new list with initial list and a procedure using map
## Foward [4]
This continue with breakfast box and explain records with a mini todo
list app.
- how to define a more complex procedure
- how to define variable inside procedures
- a short hand to make recursive procedures ie. named `let`
- how to define mutable datastructures ie. records
## Beyond [not written yet]
I don't know yet which example to use.
- goops
- values/receive
- apply
- compose
## Reference
A summary of all the syntax and procedure of the tutorial. This should
be similar to hylang tutorial.
[0]
http://docs.hylang.org/en/latest/tutorial.html#basic-intro-to-lisp-for-pythonistas
[1] http://clojurescriptkoans.com/#equality/2
[2] http://www.htdp.org/
[3] http://hypermove.net/learn-scheme-guile-basics.html
[4] http://hypermove.net/learn-scheme-guile-forward.html
next prev parent reply other threads:[~2015-10-12 20:32 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 19:23 New logo and website design proposal Luis Felipe López Acevedo
2015-09-15 19:43 ` Mathieu Lirzin
2015-09-15 23:48 ` Luis Felipe López Acevedo
2015-09-15 21:05 ` David Pirotte
2015-09-15 23:55 ` Luis Felipe López Acevedo
2015-09-16 0:12 ` Nala Ginrut
2015-09-15 21:31 ` Christopher Allan Webber
2015-09-16 0:38 ` Luis Felipe López Acevedo
2015-09-21 20:40 ` Ludovic Courtès
2015-09-23 16:18 ` Luis Felipe López Acevedo
2015-09-23 21:12 ` Ludovic Courtès
2015-10-09 22:24 ` Luis Felipe López Acevedo
2015-10-10 11:40 ` Amirouche Boubekki
2015-10-10 14:49 ` Christopher Allan Webber
2015-10-10 17:24 ` Thompson, David
2015-10-10 19:17 ` Luis Felipe López Acevedo
2015-10-11 20:11 ` Ludovic Courtès
2015-10-11 21:39 ` Luis Felipe López Acevedo
2015-10-12 13:23 ` Ludovic Courtès
2015-10-12 21:13 ` Luis Felipe López Acevedo
2015-10-18 17:58 ` Ludovic Courtès
2015-10-18 18:06 ` Luis Felipe López Acevedo
2015-10-20 12:50 ` Ludovic Courtès
2015-10-20 14:58 ` Luis Felipe López Acevedo
2015-10-20 15:05 ` Ludovic Courtès
2015-10-20 20:13 ` Luis Felipe López Acevedo
2015-10-26 23:24 ` Ludovic Courtès
2015-10-27 14:46 ` Luis Felipe López Acevedo
2015-10-27 18:15 ` Luis Felipe López Acevedo
2015-11-05 9:56 ` New web site is live! Ludovic Courtès
2015-10-12 6:07 ` New logo and website design proposal Aleix Conchillo Flaqué
2015-10-12 13:26 ` Ludovic Courtès
2015-10-12 13:06 ` tomas
2015-10-12 18:15 ` Luis Felipe López Acevedo
2015-10-12 18:59 ` tomas
2015-10-12 20:32 ` Amirouche Boubekki [this message]
2015-10-12 8:15 ` Nala Ginrut
2015-10-12 18:00 ` Luis Felipe López Acevedo
2015-10-12 17:03 ` Aleix Conchillo Flaqué
2015-10-12 18:20 ` Luis Felipe López Acevedo
2015-09-16 6:43 ` Ricardo Wurmus
2015-09-17 14:33 ` Luis Felipe López Acevedo
2015-09-16 8:19 ` Alex Sassmannshausen
2015-09-17 14:59 ` Luis Felipe López Acevedo
2015-09-17 15:09 ` Thompson, David
2015-09-18 9:47 ` Amirouche Boubekki
2015-09-23 15:17 ` Luis Felipe López Acevedo
2015-09-25 23:28 ` The Guile community we could have (or: solving Worse is More Accessible) Christopher Allan Webber
2015-09-26 8:04 ` Taylan Ulrich Bayırlı/Kammer
2015-09-26 9:04 ` Alex Sassmannshausen
2015-10-20 8:46 ` Ludovic Courtès
2015-10-20 14:48 ` Christopher Allan Webber
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=46c812a04f6d49b7ed851689abd23fcb@hypermove.net \
--to=amirouche@hypermove.net \
--cc=felipe.lopez@openmailbox.org \
--cc=guile-devel-bounces+amirouche+dev=hypermove.net@gnu.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).