[
https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Shorin resolved COUCHDB-1934.
---------------------------------------
Resolution: Fixed
[Related
discussion|http://mail-archives.apache.org/mod_mbox/couchdb-dev/201311.mbox/%3ccahdjipkrba+jtzkw8rgtcj0hbqbbraerjmjw+n1aa4ulscu...@mail.gmail.com%3E]
on ML ([nicer
view|http://www.mail-archive.com/[email protected]/msg28678.html]) - just
follow the thread.
TL;DR: jquery.couch removal is a major change that breaks a lot of couchapp
which based on it. People used it, people like it regardless will new Futon be
based on it or not: it just was too long (from very old 0.8 iirc) with CouchDB
to made it own to the project.
Summarizing all above, there are no good reasons to remove jquery.couch, but
there are a lot of to keep it. I think jquery.couch status is clearly defined -
it's active part of the project that couldn't be simply moved away from it even
in post-Futon era, so I'm closing the issue.
> jquery.couch status
> -------------------
>
> Key: COUCHDB-1934
> URL: https://issues.apache.org/jira/browse/COUCHDB-1934
> Project: CouchDB
> Issue Type: Question
> Reporter: Alexander Shorin
>
> When [~nslater] had proposed to include [jquery.couch.js
> docs|http://daleharvey.github.io/jquery.couch.js-docs/symbols/] into official
> CouchDB one I recall old good time when we had discussed Futon.Next project.
> Suddenly, it was out of official mailing lists, so no references are
> available, but [~garren], [~dch], [~bigbluehat] and [~ryanramage] were there
> and our discussion was around jquery vs backbone vs pouchdb. Backbone won.
> Nowdays, we have Fauxton which doesn't used jquery.couch and based on
> Backbone. So it seems if we'll replace Futon with him this client library
> would be left orphan.
> So that's the question: what is the status of jquery.couch.js? Is it still
> actual and supported or going to be deprecated?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
