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

Jan Lehnardt commented on COUCHDB-1934:
---------------------------------------

[~kxepal] 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. jquery.js should stay the way it is as long as we ship 
Futon.

For developers nothing changes unless they want to work on Futon. Only 
packagers will need to have the jquery.couch.js repo checked out as well (the 
details of which are to be determined and I’d love to hear from [~nslater] & 
[~djc] about options.

> 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