You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Zachary Lym (JIRA)" <ji...@apache.org> on 2014/11/08 00:01:35 UTC

[jira] [Commented] (COUCHDB-2177) Poor use of screen real-estate

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

Zachary Lym commented on COUCHDB-2177:
--------------------------------------

Sue, not sure if you really need to wait for a major UI update.  Just collapsing the fields above and below the textarea to a single row and reducing the size in the sidebar would get you most of the way there.

> Poor use of screen real-estate
> ------------------------------
>
>                 Key: COUCHDB-2177
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2177
>             Project: CouchDB
>          Issue Type: Brainstorming
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Zachary Lym
>
> Fauxton is a HUGE improvement on the UX for CouchDB.  However, the editor uses, optimistically, 20% of the available screen-space effectively:
> !http://i.imgur.com/V4l63NR.gif! 
> Obviously, this will be an ongoing task, but I would like to propose an adjustment in thinking about the map/reduce screen: we should focus on making map/reduce jobs not easier to edit but [learnable|http://worrydream.com/LearnableProgramming/].  
> I would suggest a live editing feature which pre-populates a small sample set of documents and updates interactively according to the map/reduce job (inspired by [debuggex's cool debugging interface | https://www.debuggex.com/] for regex queries).  As a beginning, I would suggest basic syntax highlighting which corresponds to fields in the actual example documents.  Eventually, this would lead to more complex highlighting of correlations between actions in the code editor and the docs themselves.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)