MIME-Version: 1.0
In-Reply-To: <1259164514-sup-196@lisa>
References: <1259164514-sup-196@lisa>
Date: Wed, 25 Nov 2009 10:33:39 -0600
Message-ID: <935ead450911250833j16359db3ob9c1d625c667ecc9@mail.gmail.com>
From: Jeffrey Ollie <jeff@ocjtech.us>
To: Scott Robinson <scott@quadhome.com>
Content-Type: text/plain; charset=UTF-8
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: [notmuch] Using notmuch from Ruby, Python, et al.
Precedence: list

On Wed, Nov 25, 2009 at 10:16 AM, Scott Robinson <scott@quadhome.com> wrote:
>
> == Shared Library
>
> I have modified the build to output a shared library. It's a small change
> relying on libtool.
>
> However, the archives indicate Carl dislikes libtool?

Ugh, please, let's not go down the autoconf/automake/libtool route.

> == JSON output
>
> I added a --output=(text|json) option to "search" and "show." Then, emit json
> results appropriately.
>
> To accomplish this, I used the cJSON library sans parsing logic.
>
> However, I saw discussion about providing a --format option?

Awesome, I was just looking at using json-glib but I haven't gotten
very far yet, mainly because I've never used it before (nor done much
of anything with JSON). I was going to call the option
'--output-format=(standard|json)' but I'm not going to worry about the
color of that bikeshed.

IMHO, I think both approaches would be valuable, that way people
writing front ends could choose the methods that worked best for them.
 Do you have patches that you are ready to share?

-- 
Jeff Ollie