From: Ariel Rios <ariel@arcavia.com>
To: Miroslav Silovic <silovic@zesoi.fer.hr>
Cc: Ariel Rios <ariel@arcavia.com>, guile-gtk@sourceware.cygnus.com
Subject: Re: What happened to sart?
Date: Wed, 06 Sep 2000 20:09:00 -0000 [thread overview]
Message-ID: <4d9004eca17830ea4a5f9c202aad6aa3@NO-ID-FOUND.mhonarc.org> (raw)
In-Reply-To: <7en1hlzqqc.fsf@zesoi.fer.hr>
> Ariel Rios <ariel@arcavia.com> writes:
>
> > What happened to sart? Anyone knows? miroslav?
>
> I really didn't have the time to develop it in the last 9-10
> months. However, I plan to resume the development in unspecified
> future (I'm toying with the idea to make that future fairly
> imminent... finished GOOPS and module system would help a lot,
> though).
Really cool... I want to do play a little with 3d graphics...
ariel
next prev parent reply other threads:[~2000-09-06 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200009060601.e8661VU20623@branka.zesoi.fer.hr>
2000-09-06 4:51 ` Miroslav Silovic
2000-09-06 20:09 ` Ariel Rios [this message]
[not found] ` <200009070309.e8739LU25468@branka.zesoi.fer.hr>
2000-09-07 3:31 ` Miroslav Silovic
2000-09-05 23:02 Ariel Rios
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4d9004eca17830ea4a5f9c202aad6aa3@NO-ID-FOUND.mhonarc.org \
--to=ariel@arcavia.com \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=silovic@zesoi.fer.hr \
/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).