Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
From: kxepal <git@git.apache.org>
To: dev@couchdb.apache.org
Reply-To: dev@couchdb.apache.org
References: <git-pr-204-couchdb-fauxton@git.apache.org>
In-Reply-To: <git-pr-204-couchdb-fauxton@git.apache.org>
Subject: [GitHub] couchdb-fauxton pull request: Update full page document
 editor
Content-Type: text/plain
Message-Id: <20150109202049.13F63816F6A@tyr.zones.apache.org>
Date: Fri,  9 Jan 2015 20:20:48 +0000 (UTC)

Github user kxepal commented on the pull request:

    https://github.com/apache/couchdb-fauxton/pull/204#issuecomment-69392835
  
    @seanbarclay The reasons behind dark theme are clear. My point was on overall design. If you're uses dark theme for code editor, you also tries to reach two other goals: turn other editor UI into the same dark theme or minimize amount of bright panels. Same problem here: we have nice dark editor for JSON code, but our attention get distracted by large light grey panels above and below it. For view browsing things getting worse since there we have a big burger of dark-light elements (dark left global sidebar, light database sidebar, dark view results table, light pagination and tabs). Design should be consistent whenever light or dark theme is used. And when it is consistent, it looks awesome.
    
    Just my 5 cents (:


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---