Where is the appropriate place to file bugs against Fuaxton? Most
recent I see in JIRA is Feb. 15th of this year.
As of a couple of hours ago when I updated my install, the view query
options UI wasn't respecting start and end keys (though the link to
the raw JSON is correct).
On Wed, Aug 19, 201
I agree with kexpal's comment on the PR; large documents would make
this very, very painful.
I was asking for a view checkbox that would result in a 3rd column for
view results (key / value / optional doc) that defaulted to off, so
that I could include it when appropriate.
Cheers,
Eli
On Wed, Au
+1
2015-08-19 17:26 GMT+02:00 Robert Kowalski :
> Thank you for your feedback!
>
> Based on the feedback we will try to enable `include_docs` per default:
>
> https://github.com/apache/couchdb-fauxton/pull/499
>
> What do you think?
>
> On Wed, Aug 19, 2015 at 9:55 AM, James Dingwall
> wrote:
>
Thank you for your feedback!
Based on the feedback we will try to enable `include_docs` per default:
https://github.com/apache/couchdb-fauxton/pull/499
What do you think?
On Wed, Aug 19, 2015 at 9:55 AM, James Dingwall
wrote:
> Eli Stevens (Gmail) wrote:
>>
>> On Tue, Aug 18, 2015 at 1:11 AM,
Eli Stevens (Gmail) wrote:
On Tue, Aug 18, 2015 at 1:11 AM, James Dingwall
wrote:
I get the impression that more whizzy effects (fade in/out, sliding divs
etc) have been added which don't play nicely with remote sessions with
low bandwidth so a preference to use more basic transitions would be
On Tue, Aug 18, 2015 at 1:11 AM, James Dingwall
wrote:
> I get the impression that more whizzy effects (fade in/out, sliding divs
> etc) have been added which don't play nicely with remote sessions with
> low bandwidth so a preference to use more basic transitions would be useful.
+1
Note that i
James Dingwall wrote:
Hi,
Following suggestions that I should try a more recent version of faxuton
I have updated some observations. I was able to easily install via npm
and point it to a CouchDB 1.6.1 installation.
Michelle Phung wrote:
One of the things I would like to cover in my presentat
> Where should I be listening to hear about when new
> fauxton releases have happened?
We don’t really do releases. We push to the repo, and then people can pull from
there.
https://github.com/apache/couchdb-fauxton
Sometimes things break, but we try to fix them right away on the master branch,
Hi Michelle,
Overall, sounds great. I'll reply inline where needed:
On Mon, Aug 17, 2015 at 10:58 AM, Michelle Phung wrote:
> Feedback #2: Default _all_docs page doesn’t show enough relevant information
> Fair enough, this is something I think we should default with
> include_docs=true,
Hi Eli!
Thanks for your writeup!
These feedback things are things we need to hear multiple times,
to really drive the message home,
so that we can be better,
address real life problems, and also
so that we can be held accountable for what we do.
Let me know if I’ve misinterpreted any of the
Hi,
Thanks for asking for user feedback!
I just installed the default new(ish?) fauxton via npm, etc. from the
instructions at https://www.npmjs.com/package/fauxton (not sure if
that's as up to date as it could be). Here are my (hopefully
constructive) opinions. In general, I agree with a lot of
gin forwarded message:
> >
> > From: James Dingwall
> > Subject: Re: Project Fauxton Feedback
> > Date: August 14, 2015 at 11:26:04 AM EDT
> > To: ,
> > Reply-To: user@couchdb.apache.org
> >
> > Michelle Phung wrote:
> >
> > One of the t
On Fri, Aug 14, 2015 at 6:39 PM, James Dingwall
wrote:
> Alexander Shorin wrote:
>>
>> On Fri, Aug 14, 2015 at 6:26 PM, James Dingwall
>> wrote:
>>>
>>> My experience of using the version of fauxton bundled in CouchDB 1.6.1
>>> (with
>>> SeaMonkey 2.33.1 in case its a browser thing...)
>>
>> You
Alexander Shorin wrote:
On Fri, Aug 14, 2015 at 6:26 PM, James Dingwall
wrote:
My experience of using the version of fauxton bundled in CouchDB 1.6.1 (with
SeaMonkey 2.33.1 in case its a browser thing...)
You definitely should try the latest Fauxton[1] (better with 2.0[2])
because their codeba
On Fri, Aug 14, 2015 at 6:26 PM, James Dingwall
wrote:
> My experience of using the version of fauxton bundled in CouchDB 1.6.1 (with
> SeaMonkey 2.33.1 in case its a browser thing...)
You definitely should try the latest Fauxton[1] (better with 2.0[2])
because their codebase difference cover one
Michelle Phung wrote:
One of the things I would like to cover in my presentation is what CouchDB
as a community, would like to see implemented in Fauxton, and what can be
improved.
My experience of using the version of fauxton bundled in CouchDB 1.6.1 (with
SeaMonkey 2.33.1 in case its a brows
Hello!
I am at the beginning of writing a presentation that I am hoping to name:
"The State of Fauxton 2015", and I would like to include community
concerns about Project Fauxton, and where we hope it will go.
One of the things I would like to cover in my presentation is what CouchDB
as a commun
17 matches
Mail list logo
