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 randall.leeds@gmail.com
 designates 209.85.160.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAL-h1aTEXESv9Ga4vA5zFYDqh8RXH3mJbmWz5tooqQL--HemWw@mail.gmail.com>
References: <054053281C1E41E9955761009CA159FF@cloudant.com>
	<C4A1A200-C7CE-498D-91CB-C84ED7405EE2@redcometlabs.com>
	<CAKmKYaBjBm1GYbCQacniMQhq0xUskojS_tTfzyc+DLNauSFhBw@mail.gmail.com>
	<D45D1C08-77F7-4BC7-9EB3-6DFD628D5A22@redcometlabs.com>
	<CAKmKYaAS=EDonCiv8eN6TEyRNu1kw8-oMPQLJiD8dA12fD2iRw@mail.gmail.com>
	<CAL-h1aQ9EaBJ=23wcabhGKZFbCwsJU8GxF_oB4NumD3jCcrEnQ@mail.gmail.com>
	<28FFE3619CC347D594B36B67A288B274@cloudant.com>
	<CAGt9U8hiFUnQGBsYFRxg32=p2_n81Jhd8e6Cc=NYJx3p0hifPQ@mail.gmail.com>
	<CAL-h1aTEXESv9Ga4vA5zFYDqh8RXH3mJbmWz5tooqQL--HemWw@mail.gmail.com>
Date: Sun, 28 Oct 2012 23:30:59 -0700
Message-ID: 
 <CAAL6JQifXe-Juudqhpuh_xWofXnVnX9gtUfbp5g3ErWD3j-CRA@mail.gmail.com>
Subject: Re: Futon.Next
From: Randall Leeds <randall.leeds@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

On Thu, Oct 25, 2012 at 10:35 AM, Ryan Ramage <ryan.ramage@gmail.com> wrote:
>>> I'd assume that in a release we'd compile things down into the share/www
>>> directory and serve out of there (as we do with the current futon, and will
>>> do with the docs), so what we need IMHO is a build tool not a couchapp push
>>> tool.
>>>
>>
>> If Futon.Next should become a proper CouchApp as discussed then we
>> certainly need a CouchApp push tool.
>
> One requirement out of Cloudant is the ability to turn things on and
> off. This will require persistance. Have a db to persistant settings
> would be a feature of using a couchapp.

That's not how I read this requirement. My understanding was that
Cloudant wanted the ability to turn off features at build
configuration time. It would affect which js files get pushed. That
means it would either effect which files grunt.js processes, or it
would affect what files get listed in some couchapp manifest.

If runtime configuration is necessary, that should be articulated more
clearly as a requirement, but I worry that this starts to balloon into
more of a CMS agree with Alexander that it starts to look like we've
gone too far.