[ 
https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843163#comment-13843163
 ] 

Alexander Shorin commented on COUCHDB-1934:
-------------------------------------------

> Alexander Shorin Not quite, I propose that the URLs remain the same. Merely 
> the source code gets moved around. On release-packaging time, jquery.couch.js 
> is pulled in from the other repo. 

I mean in long term vision (e.g. for CouchDB 3.0+). It's oblivious that for 2.x 
it will also available by old URL and new one (if any). But ok.

> jquery.js should stay the way it is as long as we ship Futon.
So when we replacing Futon with Fauxton (this will happens anyway) we also 
stops shipping with jquery.couch.js and his deps, correct? I want to clarify 
this moment since it is the main of this issue and to be sure that we all 
thinks about the same.

Sorry for such persistent questions! Thanks(:

> 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)

Reply via email to