couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Young (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1954) Clarify Futon/Fauxton transition
Date Mon, 09 Dec 2013 15:52:07 GMT

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

Benjamin Young commented on COUCHDB-1954:
-----------------------------------------

1. we keep them around until the next *major* point release.
2. added some thoughts about {{/}} routing to [COUCHDB-348|https://issues.apache.org/jira/browse/COUCHDB-348?focusedCommentId=13843248]
3. we should be sure that Fauxton routes those to their new equivalent (ideally) or en lieu
of that, not leave the user stranded (at a broken loading page or the like), but route them
to the default screen (at least).

Just ideas. :)

> Clarify Futon/Fauxton transition
> --------------------------------
>
>                 Key: COUCHDB-1954
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1954
>             Project: CouchDB
>          Issue Type: Task
>          Components: Futon
>            Reporter: Jan Lehnardt
>
> At some point Fauxton will replace Futon. There are a few questions that we should clarify
before we get there:
> 1. what happens to resources like jquery.js and jquery.couch.js that are currently in
well-known places where CouchApps depend on them?
> 2. there are several other tickets regarding serving a human readable HTML page on `/`
if the client is clearly a browser. (so people don’t have to type the `/_utils` manually,
how does that play into rolling out Fauxton?
> 3. cool URLs don’t change: what happens to links into Futon that no longer work in
Fauxton that might be coming in from the docs and other tutorials, including people’s in-house
documentation?



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message