From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] How's STS coming?
Date: Thu, 02 Oct 2008 22:21:06 +0100 [thread overview]
Message-ID: <1222982255-sup-5712@tomsk> (raw)
In-Reply-To: <slrngea0kr.sbb.0osz0s302@hole.internal.mydonutshop.org>
On 2.10.2008, Guarded Identity wrote:
> - If it's not soon to be released, do you think we can at least see the
> tree (I'm just curious to see it)
+1 on this one! I've all but given up on my web interface to current
sup. The only way I can do it properly is to pull all the ncurses code
out and then I'm going to have something that is probably fairly close
to what you're trying to do anyway in some ways so it makes more sense
to wait for STS and put some effort into coding for/with that. I ca
get something up and running against the ferret db, but then I found
myself implementing a lot of the classes/methods in sup all over and
that seemed a bit pointless as well.
Marcus
next prev parent reply other threads:[~2008-10-02 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 17:19 Sukant Hajra
2008-10-02 21:21 ` Marcus Williams [this message]
2008-10-02 22:01 ` William Morgan
2008-10-07 19:00 ` William Morgan
2008-10-13 18:14 ` William Morgan
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=1222982255-sup-5712@tomsk \
--to=marcus-sup@bar-coded.net \
/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