unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Linas Vepstas <linasvepstas@gmail.com>
To: rixed@happyleptic.org, guile-user@gnu.org, anton.vidovic@gmx.de
Subject: Re: guile user base
Date: Mon, 28 Nov 2011 10:03:38 -0600	[thread overview]
Message-ID: <CAHrUA37gRRgqLK3RHR2Onj1GvQpjJ-JO20pD=RuAxP5c8ByWbg@mail.gmail.com> (raw)
In-Reply-To: <20111128094231.GA20529@ccellier.rd.securactive.lan>

On 28 November 2011 03:42,  <rixed@happyleptic.org> wrote:
>
> - but
> that's not my intent for many reasons (mostly, I think guile is more
> useful as a free software extension tool than as a general programming
> learning tool, but this is of topic).

Well, not really. People get involved in stages, steps, ladders. For
example, someone might want to modify some part of gnucash in some
way.  Maybe a few lines of scheme will do. This step taken, the doors
now open to a deeper understanding of guile. Each of these doors in
turn lead to others.  At some point, the casual user becomes an active
member of the community.

So: I think gnucash represents a non-trivial example of guile as an
extension language. I think it would be excellent if there were
tutorials for how to actually extend gnucash, using guile. As far as I
know, none exist.  Ditto lillypond, geda, or aisleriot, if accounting
is not your bag.

I mean: what's the point of an extension language if no one knows how
to use it to extend anything? This is where the code should be laid
bare: its hard to screw with it when its cloaked by the app.  What are
extension best practices?  What paradigm/api/style can can a guile
programmer expect all guile-using apps to provide?  Some standardized,
easy, obvious way to extend an app, in a fashion that works more or
less the same way for all apps?  All this info is missing.

--linas



  reply	other threads:[~2011-11-28 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 23:39 guile user base rixed
2011-11-27 22:23 ` Ludovic Courtès
2011-11-28  0:14   ` Linas Vepstas
2011-11-28 13:00     ` Ludovic Courtès
2011-11-28 13:25       ` Peter Brett
2011-11-28 22:42         ` Ludovic Courtès
2011-11-28  9:42 ` rixed
2011-11-28 16:03   ` Linas Vepstas [this message]
2011-11-28 22:50   ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2011-11-24 20:29 Anton Vidovic

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='CAHrUA37gRRgqLK3RHR2Onj1GvQpjJ-JO20pD=RuAxP5c8ByWbg@mail.gmail.com' \
    --to=linasvepstas@gmail.com \
    --cc=anton.vidovic@gmx.de \
    --cc=guile-user@gnu.org \
    --cc=rixed@happyleptic.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).