Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: Andreas Happe <andreashappe@snikt.net>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup web interface
Date: Thu, 03 Jun 2010 11:16:32 -0400	[thread overview]
Message-ID: <1275577785-sup-679@zyrg.net> (raw)
In-Reply-To: <loom.20100603T150837-186@post.gmane.org>

Excerpts from Andreas Happe's message of 2010-06-03 09:11:31 -0400:
> Rich Lane <rlane <at> club.cc.cmu.edu> writes: 
> > This is a great idea. I recommend using the sup-server protocol, either
> > natively or by running sup-cmd. That code has been in master for a while
> > now. I don't have a real opinion on web frameworks, but I'm biased
> > towards something lightweight.
> 
> Wouldn't Rails[0] be the most obvious candidate? In addition since merb[1] was
> merged (during the ongoing 3.0 development cycle) it might even count as
> lightweight..

Sure. I really don't care what framework is used, I'll be happy just to
see a working web UI. At the time I was thinking that if the web UI code
were small enough it would be reasonable to keep it in the main Sup repo,
but now I'm not even sure that's desirable.

> I won't start it (as I don't have nearly enough time on my hand), but might
> contribute -- just put a rough (but working) prototype on github.

Link?
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-06-03 15:17 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 [this message]
2010-06-04 12:01       ` Andreas Happe
2010-06-04 15:59         ` Jason Petsod
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=1275577785-sup-679@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    --cc=andreashappe@snikt.net \
    --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