Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Jason Petsod <jason@petsod.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup web interface
Date: Fri, 04 Jun 2010 10:59:15 -0500	[thread overview]
Message-ID: <1275666025-sup-4912@acheron.quadco.net> (raw)
In-Reply-To: <loom.20100604T135436-725@post.gmane.org>

On 04/06/2010 at 07:01:08 -0500, Andreas Happe wrote:
> To github[0]? My last sentence could have been clearer: I haven't put anything
> sup-related up on github, but if someone starts with a rough, but working,
> prototype I could help out.

I was able to start working on this a little bit [1] but it's currently
very rough around the edges. It uses the Sinatra framework, but most of the
actual logic is framework-agnostic so it could be pretty easily adapted
for another framework.

For threading, I had to add a new command 'thread' to sup-server, so you'll
need to apply a patch [2] before it works. The threading logic still needs
a little work; I roughly adapted sup's thread.rb, but added some bugs for
good measure :)

Also, it's not evident to me that the sup-server polls for new messages or
has the ability to add new messages to the index, so checking for new
messages or sending emails doesn't work yet. That functionality shouldn't
hard to add though.

Cheers,
-Jason

[1] http://github.com/jasonpetsod/sup-web
[2] http://github.com/jasonpetsod/sup-web/raw/master/misc/expose_threading_on_sup-server.diff
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-06-04 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30  5:43 Jason Petsod
2010-04-30 14:17 ` Nicholas Bergson-Shilcock
2010-04-30 14:57   ` Jon Dugan
2010-04-30 23:13 ` Rich Lane
2010-06-03 13:11   ` Andreas Happe
2010-06-03 15:16     ` Rich Lane
2010-06-04 12:01       ` Andreas Happe
2010-06-04 15:59         ` Jason Petsod [this message]
2010-06-05  3:55           ` Rich Lane

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=1275666025-sup-4912@acheron.quadco.net \
    --to=jason@petsod.org \
    --cc=sup-talk@rubyforge.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