couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Lehnardt (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1934) jquery.couch status
Date Mon, 09 Dec 2013 14:08:09 GMT

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

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

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

Great question. This is out of scope for this ticket, I’d say. There are a few other factors
that play into that (like what to server at / for no-json clients (e.g. a human-readable start
page). Let’s file a new issue for all this: https://issues.apache.org/jira/browse/COUCHDB-1954

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

Mime
View raw message