From user-return-15690-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Thu Apr 07 07:55:01 2011 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 32135 invoked from network); 7 Apr 2011 07:55:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Apr 2011 07:55:01 -0000 Received: (qmail 76432 invoked by uid 500); 7 Apr 2011 07:55:00 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 76098 invoked by uid 500); 7 Apr 2011 07:54:59 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 76090 invoked by uid 99); 7 Apr 2011 07:54:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Apr 2011 07:54:59 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rasmussen.bryan@gmail.com designates 209.85.210.180 as permitted sender) Received: from [209.85.210.180] (HELO mail-iy0-f180.google.com) (209.85.210.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Apr 2011 07:54:51 +0000 Received: by iyf40 with SMTP id 40so3607709iyf.11 for ; Thu, 07 Apr 2011 00:54:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=Q4P/qfccAUBqpnwR2+eMlvz9PZ4PMeL2gtV6LP+upF8=; b=NEWGItrcRp+fOC4RDHO2G4UaaycQJn8CNrBYsBl9jWBHdgIvXGsb5WuEblUEUtSgrR TNmNVK4jrrAZGKSqxBjx66zezLehReXZKBQnFcF1RoQGLp2B3i+A47G2opJtGaiDzU/M 04uATMydI174XhTjYni2TmzKhRwJZGSyIY8jw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=wugha+EogjGerQkda4kL1h9hvGC5TSQq38iZql3Kq4OwDIsV4oI1uILQEdPDAmTOdm 8s0Uuvdqu0zQx428Yf/fsqZrLOszzdl8G3nA4gmgL6CLCHhGLNdi/lZ9LDNP4oeTY+wy sSZeBGTCBkEMYaXijpVk+Z9kKPu1FvQpGA5B0= MIME-Version: 1.0 Received: by 10.43.69.199 with SMTP id yd7mr901368icb.370.1302162870110; Thu, 07 Apr 2011 00:54:30 -0700 (PDT) Received: by 10.42.239.1 with HTTP; Thu, 7 Apr 2011 00:54:30 -0700 (PDT) In-Reply-To: References: Date: Thu, 7 Apr 2011 09:54:30 +0200 Message-ID: Subject: Re: The new couchapp. [cr] From: bryan rasmussen To: user@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org 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) Thanks, Bryan Rasmussen On Wed, Apr 6, 2011 at 10:13 PM, Hendrik Jan van Meerveld wrote: > Hi Beno=C3=AEt, > > 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. > > 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 Erla= ng > first. > This way it will take normal users more time (learning time + edit time) = to > change the config file. > > Also if you translate your snippet from Erlang to JSON I think it will no= t > be much more complex to edit. > > > Kind regards, > Hendrik Jan > > On 6 April 2011 18:58, Marcello Nuccio wrote: > >> What are the advantages of using erlang for the config file? >> Scriptability? >> >> thanks, >> =C2=A0Marcello >> >> 2011/4/6 Benoit Chesneau : >> > On Wed, Apr 6, 2011 at 1:10 PM, Hendrik Jan van Meerveld >> > wrote: >> >> Hi Beno=C3=AEt, >> >> >> >> Thanks for working on improving couchapp which is allready great. >> >> >> >> Would an Erlang config file be readable for a non-Erlang person like = me? >> >> What would it look like? >> >> >> > >> > Here is a snippet of current work (not public yet): >> > >> > % log level >> > {verbose_level, =C2=A01}. >> > >> > % always check app on sent >> > {always_check, true}. >> > >> > % dbs urls >> > {push_env, [ >> > =C2=A0 =C2=A0% one db push >> > =C2=A0 =C2=A0 {"name", "url", [Options]}, >> > =C2=A0 =C2=A0 % multiples db push >> > =C2=A0 =C2=A0 {"name", [{url option}, {url, options}]} >> > ]}. >> > >> > % hooks >> > {pre_hooks, [{push, "path/to/shell'}}}. >> > {post_hooks, [{push, "path/to/shell'}}}. >> > >> > >> > I think it's enough simple to be used by anyone, isn't it? >> > >> > - beno=C3=AEt >> > >> >