You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/02/03 12:08:34 UTC
[jira] [Commented] (COUCHDB-2565) Responsive Fauxton
[ https://issues.apache.org/jira/browse/COUCHDB-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303087#comment-14303087 ]
ASF GitHub Bot commented on COUCHDB-2565:
-----------------------------------------
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/253#issuecomment-72632759
Those are great ideas and suggestions!
Sadly I don't have the time to make Fauxton fully responsive and can just fix the most major annoying bugs.
For a full responsive Fauxton I think we would need:
- throw out the current not maintained Bootstrap 2 which is mainly just used for button styling at the moment
- make use of an actively maintained bootstrap and use it's helper to create responsive grids
I documented this together with your ideas in Jira: https://issues.apache.org/jira/browse/COUCHDB-2565
Can you describe the issue you have regarding the database-searchlabel or create an video?
> Responsive Fauxton
> ------------------
>
> Key: COUCHDB-2565
> URL: https://issues.apache.org/jira/browse/COUCHDB-2565
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Fauxton
> Reporter: Robert Kowalski
>
> For a full responsive Fauxton I think we would need:
> - throw out the current not maintained Bootstrap 2 which is mainly just used for button styling at the moment
> - make use of an actively maintained bootstrap and use it's helper to create responsive grids
> Some good points from [~michellep]:
> Suggestions:
> 1. We could collapse the left most nav when the screen is below a certain width.
> 2. Also maybe when the width gets really small, collapse the api url/ add new database/ search buttons down to icon-only (like in buttons the code editor).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)