Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of nslater@tumbolia.org
 designates 209.85.223.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5061A0D4.7090308@bigbluehat.com>
References: 
 <CAJNb-9p5+oWTqMrYXwvkHyFnuHn-Fg_RNHyLAexuX7LcNMV-gg@mail.gmail.com>
	<D9235C8A8D2B42C7B042ABBB28080C4A@cloudant.com>
	<CA+Y+444P9u73tuWJjx34R1uYb7bcW0DWAhGfGjBEiAUrms9hTQ@mail.gmail.com>
	<5061A0D4.7090308@bigbluehat.com>
Date: Tue, 25 Sep 2012 13:37:30 +0100
Message-ID: 
 <CA+Y+446zOczfp7cOWpoBRC80oiRni-LMxKd2Q9UaXphRufC+Bg@mail.gmail.com>
Subject: Re: Part2: What's up dev? About couchapps.
From: Noah Slater <nslater@tumbolia.org>
To: dev@couchdb.apache.org
Content-Type: multipart/alternative; boundary=e89a8f83883b3a878e04ca85f8f3

--e89a8f83883b3a878e04ca85f8f3
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Sep 25, 2012 at 1:17 PM, Benjamin Young <byoung@bigbluehat.com>wrote:

>
> The common denominator of the filesystem-to-design-doc mapping [1] among
> the Python "couchapp", erica, and kanso's "traditional-couchapp" dependency
> [2] is an advantage and that shouldn't be given up lightly.
> node.couchapp.js could certainly be made (with minimal app.js or a new
> require() option) to load all the assets from this same filesystem mapping.
>
> If nothing else, it would mean that when anyone says "I built a CouchApp"
> anyone else knows what that looks like on disk, and where to find what.
> Then the tools become value adds, not requirements.


Huh. That's a very good point indeed. Standardisation.

-- 
NS

--e89a8f83883b3a878e04ca85f8f3--