[
https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843142#comment-13843142
]
Alexander Shorin commented on COUCHDB-1934:
-------------------------------------------
[~janl] , sounds very good! I'm happy to +1, but one question:
> bundle it on build-time with CouchDB, so CouchApps don’t break right away.
So as for CouchDB users we just moving jquery.couch _and_ his dependencies
(like jquery.js), but not futon one(like jquery.ui.js etc.) to some other
location (like /_static/scripts). Correct? Btw, having separate from
Futon/Fauxton resource for such static content that supposed to be used by
couchapp might be good idea.
As for developers jquery.couch will live in his own new repo and when they
builds the CouchDB they may run ./configure with option `--with-jquery-couch`
(or without?) to let autotools grab jquery.couch with all his actual deps to
the release artifact?
> 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.4#6159)