While this hasn’t kept us back from upgrading to Couch 2, we have run into some similar challenges with Fauxton. I think they would be fairly simply fixed by adding in some UI for functionality already in the Ace editor.
Settings for code folding—it’d be nice (for us) to have the JSON documents folded by default. Even better would be the ability to set a preference as to how many levels should be unfolded by default, and saved in the browser’s local storage or something. That would help us a lot in navigating deeply nested JSON documents where the top levels usually have all the data we need when debugging. Search functionality. It looks like the browser’s search doesn’t work, since Ace is probably doing virtual scrolling (i.e. only putting the text in the DOM that’s on the screen at the time. Ace appears to have some search functionality, but it would need some UI around it. Again, they haven’t kept us back from upgrading, but they are some of the concerns I’ve heard from our developers when we *did* upgrade. David Alan Hjelle 1 Corinthians 2:2 http://thehjellejar.com/ <http://thehjellejar.com/> <http://thehjellejar.com/>See the church management software I build at Icon Systems, Inc. <http://iconcmo.com/> Check out Rita’s spoons <http://jarofwood.com/>. > On Jul 5, 2018, at 2:32 AM, Kai Griffin <k...@resourceandrevenue.com> wrote: > > As developers who spend a lot of time in the CouchDB web interface, we have > held back moving to CouchDB 2.x only because of the change from Futon to > Fauxton. We feel that Fauxton simply does not meet the needs of developers > as well as Futon did. It seems to be targeted more at non-devs: it’s very > friendly-looking, modern & pretty, but is biased towards prettifying document > JSON, at the expense of being able to scan through many unformatted > documents, which Futon does by default. > > So, mainly comes down to the inability to properly see the contents of > documents without opening up documents individually. We like to see the > whole, unformatted document when viewing a list of documents (or, in the case > of looking at a View, then whatever the map script outputs, but in an > unformatted form, not prettified like Fauxton). Futon is more compact & > developer friendly, even if to a non-dev, such views might look like a jumble > of unformatted text. At very least, some kind of “classic mode” switch would > be greatly welcomed, at least by us :-) > > Please note that it’s been awhile since I’ve looked at CouchDB 2.x, and the > issue I brought up above might well have been addressed by someone in the > meantime, so apologies if I’m dredging up old/non-relevant stuff (in which > case we’ll happily jump onto 2.x!) > > > On 5 July 2018 at 09:21:37, Andrea Brancatelli (abrancate...@schema31.it) > wrote: > > Well, mine is the lack for a working FreeBSD port for CouchDB 2.x... > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218844 > > On 2018-07-05 09:10, Johs Ensby wrote: > >> This thread reach out to CouchDB 1.x users to generate a list of >> "must-fix" issues that is preventing users to upgrade to the latest >> version of CouchDB. >> >> It is in response to Joan's comment below regarding the >> non-technical proposal to make a project decision to terminate >> official Apache support for CouchDB 1.x. >> >>> On 5 Jul 2018, at 06:31, Joan Touzet <woh...@apache.org> wrote: >>> >>> As for things in 2.x that are "must fix" before people can upgrade, I >>> too would like to see pull requests for those. Once again, your help is >>> most welcome in this - both in identifying a definitive list of those >>> must-fix issues, as well as code towards fixing them. If you'd like >>> to help with this important work, please start a new thread. >> >> Mine is CouchDB as a proxy. >> The feature described here is not working in 2.1.1 >> http://docs.couchdb.org/en/2.1.1/config/proxying.html?highlight=_proxy >> >> Johs
