From: Tom Lord <lord@emf.net>
Cc: guile-user@gnu.org, ttn@glug.org, guile-devel@gnu.org
Subject: ITLA (was Re: Arch and Guile)
Date: Mon, 1 Mar 2004 11:04:02 -0800 (PST) [thread overview]
Message-ID: <200403011904.LAA20046@morrowfield.regexps.com> (raw)
In-Reply-To: <87n0707icl.fsf_-_@alice.rotty.yi.org> (message from Andreas Rottmann on Mon, 01 Mar 2004 15:27:38 +0100)
> From: Andreas Rottmann <a.rottmann@gmx.at>
> Using Arch would also make stuff easier for the "mainstream" Guile
> developers to maintain their stable and development branches: They
> could have an guile--fixes--1.6 branch, wich they'd simple star-merge
> into HEAD.
Should work in this area start to take place, please let me know if I
can help in any way.
> I'm not totally clear what you mean here, and how that relates to an
> Arch<->CVS gateway. Anyway, you might be interested in my ITLA
> thingy[0].
You appear to have left out the footnote.
I'd like to point out some info about the ITLA idea. ITLA is not, at
it's core, tla specific -- it's a generic engine for making
interactive Scheme programs, both CLI and GUI.
See:
http://mail.gnu.org/archive/html/gnu-arch-users/2003-11/msg00291.html
Particularly the section "How it Would Work" which begins:
* How it Would Work
ITLA would be written as an "extensible shell".
Most likely, especially since arch is a GNU project, in Guile.
SCSH, MzScheme, and Systas Scheme are other possibilities.
It's architecture would somewhat resemble Emacs' in the following
way: [....]
The ITLA framework is one of the target applications for Pika Scheme
but it will be a long time before Pika is ready to start implementing
it. There's no reason not to start on the framework earlier, using
Guile (and many good reasons to do so).
-t
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-03-01 19:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 3:32 Extended -e syntax Clinton Ebadi
2004-03-01 5:04 ` Andreas Rottmann
[not found] ` <E1AxlJY-0002cb-00@surf.glug.org>
2004-03-01 14:27 ` Arch and Guile Andreas Rottmann
2004-03-01 19:04 ` Tom Lord [this message]
2004-03-01 19:14 ` ITLA Andreas Rottmann
2004-03-01 21:55 ` ITLA Tom Lord
2004-03-02 0:11 ` ITLA Andreas Rottmann
2004-03-02 2:50 ` ITLA Tom Lord
2004-03-02 14:04 ` ITLA Andreas Rottmann
2004-03-02 3:26 ` ITLA Miles Bader
2004-03-03 11:22 ` ITLA Neil Jerram
2004-03-03 11:55 ` ITLA Andreas Rottmann
2004-03-06 15:47 ` ttn's build system [was: Extended -e syntax] Andreas Rottmann
[not found] ` <E1AziNk-0007mW-00@surf.glug.org>
2004-03-06 20:39 ` ttn's build system Andreas Rottmann
2004-03-10 18:59 ` Andreas Rottmann
2004-03-10 22:28 ` ttn's build system [was: Extended -e syntax] Clinton Ebadi
2004-03-10 23:22 ` Tom Lord
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=200403011904.LAA20046@morrowfield.regexps.com \
--to=lord@emf.net \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=ttn@glug.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).