Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of rgabo@rgabostyle.com designates
 209.85.161.52 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: The new couchapp. [cr]
From: Gabor Ratky <rgabo@rgabostyle.com>
In-Reply-To: <BANLkTikC_xEeFujdwvcKtGoVkKOS2cG_yQ@mail.gmail.com>
Date: Thu, 7 Apr 2011 13:12:01 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E468944-830B-4B90-827C-410C631E9F66@rgabostyle.com>
References: <BANLkTi=pYCJDHgNOhurL7zv4gd4pk+nsWw@mail.gmail.com>
 <BANLkTinxMTzgcrWajFsoiU5mg8ZoDrXtWw@mail.gmail.com>
 <BANLkTi=bNEEieB5WQg4mxoRpBa8JXkJT+w@mail.gmail.com>
 <BANLkTikVKQp2fBAqAARizEkO3UOXgR7Lxg@mail.gmail.com>
 <BANLkTikFozyaFWBZ=Hv_GRiUcvvHpKp=Ew@mail.gmail.com>
 <BANLkTikmea1FeV8r06ekf-veGr5aNq+MAQ@mail.gmail.com>
 <BANLkTikC_xEeFujdwvcKtGoVkKOS2cG_yQ@mail.gmail.com>
To: user@couchdb.apache.org

Don't mean to be negative wrt the original python couchapp and the new =
one in development, but we've moved over to soca (sammy on couchapp) =
that comes with a nice ruby (thor-based) CLI. It also lets go of the =
quirky, albeit logical directory structure that couchapp enforces on =
you. It loses 'clone' functionality in the process but we end up with a =
much more straightforward project where its much easier to use =
coffeescript, compass as post-build pre-push hooks and extending it is =
also very simple. It also comes with Sammy.js instead of evently which I =
find much better suited for couchapps (being a Sinatra fan, to be fair).

Being a Ruby shop, it was the logical move for us but in general I find =
it a lot easier to comprehend and to work with. Having an Erlang =
configuration file suddenly pop up in my couchapp would not help the =
situation.

Gabor

On Apr 7, 2011, at 9:54 AM, bryan rasmussen wrote:

> I would also prefer JSON. There are lots of tools to emit and
> manipulate JSON, in my current build scenarios I am using javascript
> to maintain and generate configurations, that would have to change
> with erlang based configuration (or would at any rate need some new
> coding)
>=20
> Thanks,
> Bryan Rasmussen
>=20
> On Wed, Apr 6, 2011 at 10:13 PM, Hendrik Jan van Meerveld
> <haaiee@gmail.com> wrote:
>> Hi Beno=EEt,
>>=20
>> It does look readable and usable, but I have to agree with Sean that =
JSON
>> would be much easier.
>> Most users know JSON and don't know Erlang.
>>=20
>> Probably for you as a developer, changing the config file often, it =
will be
>> easier or faster to edit in Erlang.
>> For users that edit the file only once, they need time to learn some =
Erlang
>> first.
>> This way it will take normal users more time (learning time + edit =
time) to
>> change the config file.
>>=20
>> Also if you translate your snippet from Erlang to JSON I think it =
will not
>> be much more complex to edit.
>>=20
>>=20
>> Kind regards,
>> Hendrik Jan
>>=20
>> On 6 April 2011 18:58, Marcello Nuccio <marcello.nuccio@gmail.com> =
wrote:
>>=20
>>> What are the advantages of using erlang for the config file?
>>> Scriptability?
>>>=20
>>> thanks,
>>>  Marcello
>>>=20
>>> 2011/4/6 Benoit Chesneau <bchesneau@gmail.com>:
>>>> On Wed, Apr 6, 2011 at 1:10 PM, Hendrik Jan van Meerveld
>>>> <haaiee@gmail.com> wrote:
>>>>> Hi Beno=EEt,
>>>>>=20
>>>>> Thanks for working on improving couchapp which is allready great.
>>>>>=20
>>>>> Would an Erlang config file be readable for a non-Erlang person =
like me?
>>>>> What would it look like?
>>>>>=20
>>>>=20
>>>> Here is a snippet of current work (not public yet):
>>>>=20
>>>> % log level
>>>> {verbose_level,  1}.
>>>>=20
>>>> % always check app on sent
>>>> {always_check, true}.
>>>>=20
>>>> % dbs urls
>>>> {push_env, [
>>>>    % one db push
>>>>     {"name", "url", [Options]},
>>>>     % multiples db push
>>>>     {"name", [{url option}, {url, options}]}
>>>> ]}.
>>>>=20
>>>> % hooks
>>>> {pre_hooks, [{push, "path/to/shell'}}}.
>>>> {post_hooks, [{push, "path/to/shell'}}}.
>>>>=20
>>>>=20
>>>> I think it's enough simple to be used by anyone, isn't it?
>>>>=20
>>>> - beno=EEt
>>>>=20
>>>=20
>>=20