Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 99373 invoked from network); 17 Feb 2009 18:09:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Feb 2009 18:09:20 -0000 Received: (qmail 67754 invoked by uid 500); 17 Feb 2009 18:09:19 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 67727 invoked by uid 500); 17 Feb 2009 18:09:19 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 67716 invoked by uid 99); 17 Feb 2009 18:09:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Feb 2009 10:09:19 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates 209.85.221.21 as permitted sender) Received: from [209.85.221.21] (HELO mail-qy0-f21.google.com) (209.85.221.21) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Feb 2009 18:09:11 +0000 Received: by qyk14 with SMTP id 14so3749677qyk.11 for ; Tue, 17 Feb 2009 10:08:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=CpD4BoKfO4w+3539FF56tmz4Go7KT2l6upAu3Fqg7T0=; b=OPlhkMgjwoGQa9X+9o/Mfid84eL90tErLmlgaJFXwhhmV70UTh6J/yHqcfHsgh5L+Q K1S2pRTFE4eDAEGwh4hvgwtshp8EvJ/ozVqEkOoWrSCkhl1/ivSYENJp0++aBj/kK83Q 2zm0fnCAuEbpsrLgdWdopPBBiXXfqr/LMD3oI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=CdNQLJeA8nzkn+E/MhSAvjjM9LjzBI5/cdMKUub5VRQnhfs0jj+Mg8N1qJt5JCy4rm i3oUx2cVkZxB7jvZXieFAcIPXQEYF5OPZPpy6VYS7ugflkPXhhTU+KBeU2atJ+KApRjH yDxJYVeyInwfrUwBWiufHTsI++RDSQvtZiTEc= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.224.15.11 with SMTP id i11mr6651582qaa.2.1234894130178; Tue, 17 Feb 2009 10:08:50 -0800 (PST) In-Reply-To: <09EC2DE9-8995-4EFB-A1CA-CF0A2E3C7844@apache.org> References: <790ECCEC-49A1-4766-AD91-05DC06FACA03@apache.org> <09EC2DE9-8995-4EFB-A1CA-CF0A2E3C7844@apache.org> Date: Tue, 17 Feb 2009 10:08:50 -0800 X-Google-Sender-Auth: 7edd9028522b539f Message-ID: Subject: Re: Futon Future From: Chris Anderson To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Feb 17, 2009 at 9:47 AM, Jan Lehnardt wrote: > > On 17 Feb 2009, at 18:18, Damien Katz wrote: >> >> On Feb 17, 2009, at 6:53 AM, Jan Lehnardt wrote: >>> List of installed apps. With CouchApps shaping up, Futon could show a >>> list of >>> installed applications alongside created databases. The way to detect >>> CouchApps >>> is not yet defined, though there are sensible proposals. >> >> I don't dislike this idea, but this seems more like an end user feature? >> Like a start menu for CouchApps? I think most end users (as opposed to devs >> and admins) should never need to use Futon. > > This is meant for a dev managing multiple CouchApps, not an end user. I > agree > that Futon is not an end-user tool. Granted, the line with user and dev is > blurry > with CouchApps, but this would make a dev's live easier to get a list of > apps instead > of hunting attachments in design docs (3-4 clicks at least). Yes, > bookmarks..., but still :) > I'm working on code to detect CouchApps, and adding it to Futon is the first place I can think of to put it. I think once devs have had a chance to file off the rough edges, we can think about another global handler for users (maybe /_apps ?) that will list all end-user friendly design docs that are available on a particular node. Ideally this would be an HTML representation available at "/" but currently we're using that path for node info. Chris -- Chris Anderson http://jchris.mfdz.com