Ben Keen (JIRA | 24 Nov 23:58 2014
Picon

[jira] [Commented] (COUCHDB-2390) Fauxton config, admin sections considered dangerous in 2.0


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

Ben Keen commented on COUCHDB-2390:
-----------------------------------

My previous idea didn't meet with much approval (fine fine, it *was* a hack) and I'm rather out of ideas.

To sum up, without backend support, all we can really do is add a message to the page saying "This applies to
the current node only" on the Config + Create Admin pages - with maybe some additional explanatory blurb.
The message would only ever appear for 2.x, not 1.x.

All considered, I think that would be better than removing the functionality altogether.

> Fauxton config, admin sections considered dangerous in 2.0
> ----------------------------------------------------------
>
>                 Key: COUCHDB-2390
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2390
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: BigCouch, Fauxton
>            Reporter: Joan Touzet
>            Priority: Blocker
>
> In Fauxton today, there is are 2 sections to edit config-file settings and to create new admins. Neither of
these sections will work as intended in a clustered setup.
(Continue reading)

Ben Keen (JIRA | 24 Nov 22:56 2014
Picon

[jira] [Assigned] (COUCHDB-2479) Add option to PUT config setting


     [
https://issues.apache.org/jira/browse/COUCHDB-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ben Keen reassigned COUCHDB-2479:
---------------------------------

    Assignee: Ben Keen

> Add option to PUT config setting
> --------------------------------
>
>                 Key: COUCHDB-2479
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2479
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Ben Keen
>            Assignee: Ben Keen
>
> This is very much secondary to figuring out this ticket: 
> https://issues.apache.org/jira/browse/COUCHDB-2390
> But it feel conspicuously absent not being able to update an existing setting, just delete then recreate.

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

(Continue reading)

Ben Keen (JIRA | 24 Nov 22:56 2014
Picon

[jira] [Created] (COUCHDB-2479) Add option to PUT config setting

Ben Keen created COUCHDB-2479:
---------------------------------

             Summary: Add option to PUT config setting
                 Key: COUCHDB-2479
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2479
             Project: CouchDB
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Fauxton
            Reporter: Ben Keen

This is very much secondary to figuring out this ticket: 
https://issues.apache.org/jira/browse/COUCHDB-2390

But it feel conspicuously absent not being able to update an existing setting, just delete then recreate.

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

Ben Keen (JIRA | 24 Nov 22:52 2014
Picon

[jira] [Commented] (COUCHDB-2390) Fauxton config, admin sections considered dangerous in 2.0


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

Ben Keen commented on COUCHDB-2390:
-----------------------------------

How about something like this. It’s fussy, but I think it’s better than removing the config + admin
sections altogether. And it will at least allow the config page to function properly in both a cluster and
non-cluster setup.

On the config page, detect the couchdb version.

*1.x*
Continue showing it just like now. No problemo.

*2.x*
Case 1: If CORS *isn’t* enabled on one or more more of the nodes in the cluster, add a message at the top of the
screen saying:

{quote}
One or more of the nodes in your cluster doesn’t have CORS enabled. If you want to update any of the config
settings below you will need to manually make the change to each node. Here are the list of nodes on your cluster:

	node1 (CORS enabled)
	node2 (CORS not enabled)
	node3 (CORS not enabled)

If you enable CORS on all servers you can update all node configs with a single action. Learn more.”
(Continue reading)

Ben Keen (JIRA | 24 Nov 20:33 2014
Picon

[jira] [Resolved] (COUCHDB-2467) Minor flashing over breadcrumbs during route changes


     [
https://issues.apache.org/jira/browse/COUCHDB-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ben Keen resolved COUCHDB-2467.
-------------------------------
    Resolution: Fixed

> Minor flashing over breadcrumbs during route changes
> ----------------------------------------------------
>
>                 Key: COUCHDB-2467
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2467
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Ben Keen
>            Assignee: Ben Keen
>
> Neat CSS issue. After fixing COUCHDB-2465 I noticed the problem wasn't 100% fixed... There's a sort of
quick flashing that appears over the breadcrumbs section on the Database pages when changing routes.
> To reproduce: 
> 1. In Chrome (looks fine in FF), go to the Database -> All Docs page for a database.
> 2. Click from the All Documents page to All Design Docs.
> Note: it's subtle! And it only occurs on Chrome, not Firefox. Notice that there's a sort of quick white
flash that appears over the breadcrumbs section - making it look a little like the breadcrumbs are being
re-rendered (they're not any more, thanks to COUCHDB-2465 :) ).
> This is due to a combination of the document <footer>'s position:fixed and the parent #dashboard element
not being explicitly set to 100%. For some reason on Chrome it briefly gets rendered at the top of the page.
(Continue reading)

Alexander Shorin (JIRA | 24 Nov 19:16 2014
Picon

[jira] [Commented] (COUCHDB-2390) Fauxton config, admin sections considered dangerous in 2.0


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

Alexander Shorin commented on COUCHDB-2390:
-------------------------------------------

[~garren], I remember from our very first ML thread about Fauxton there were the plans to make it
multiserver and switch target CouchDB url with easy (like thought "Connect to node ..." button). Is that
possible now or will it be hard to implement with current design?

> Fauxton config, admin sections considered dangerous in 2.0
> ----------------------------------------------------------
>
>                 Key: COUCHDB-2390
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2390
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: BigCouch, Fauxton
>            Reporter: Joan Touzet
>            Priority: Blocker
>
> In Fauxton today, there is are 2 sections to edit config-file settings and to create new admins. Neither of
these sections will work as intended in a clustered setup.
> Any Fauxton session will necessarily be speaking to a single machine. The config APIs and admin user info
as exposed will only add that information to a single node's .ini file.
> We should hide these features in Fauxton for now (short-term fix) and correct the config /admin creation
APIs to work correctly in a clustered setup (medium-term fix).
(Continue reading)

Alexander Shorin (JIRA | 24 Nov 19:12 2014
Picon

[jira] [Resolved] (COUCHDB-2149) Use stale views


     [
https://issues.apache.org/jira/browse/COUCHDB-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Shorin resolved COUCHDB-2149.
---------------------------------------
    Resolution: Fixed

> Use stale views
> ---------------
>
>                 Key: COUCHDB-2149
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2149
>             Project: CouchDB
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Alexander Shorin
>            Assignee: Sue Lockwood
>
> Futon allows this

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

Alexander Shorin (JIRA | 24 Nov 19:12 2014
Picon

[jira] [Commented] (COUCHDB-2149) Use stale views


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

Alexander Shorin commented on COUCHDB-2149:
-------------------------------------------

You're right: I was confused. This only proves the fact that the same UI element should looks and works the
same all the time without any specifics about current page environment. But that's a question to UX
experts (:

> Use stale views
> ---------------
>
>                 Key: COUCHDB-2149
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2149
>             Project: CouchDB
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Alexander Shorin
>            Assignee: Sue Lockwood
>
> Futon allows this

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

(Continue reading)

Robert Kowalski (JIRA | 24 Nov 19:10 2014
Picon

[jira] [Assigned] (COUCHDB-2471) Rewrite CSS for Header and Pane-Layout


     [
https://issues.apache.org/jira/browse/COUCHDB-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Kowalski reassigned COUCHDB-2471:
----------------------------------------

    Assignee: Robert Kowalski

> Rewrite CSS for Header and Pane-Layout
> --------------------------------------
>
>                 Key: COUCHDB-2471
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2471
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Robert Kowalski
>            Assignee: Robert Kowalski
>         Attachments: cloudant_dashboard_functional_prototype.zip
>
>
> There are several issues with our current pane-layout and the header, their width is controlled by resizeColumns.js:
>  - We are often getting horizontal scrollbars which are quite hard to fix
(https://issues.apache.org/jira/browse/COUCHDB-2234) - as soon as we fix them the issues return
almost immediately after fixing them: https://issues.apache.org/jira/browse/COUCHDB-2320 
>  - Multipane Layouts and Header in Multipane Layouts are overlapping and this leads to interesting bugs
and workarounds. Examples are: 
>   1. Button not clickable (as it is overlapped by a not visible other header element of the panes)
(Continue reading)

Picon

[jira] [Commented] (COUCHDB-2467) Minor flashing over breadcrumbs during route changes


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

ASF subversion and git services commented on COUCHDB-2467:
----------------------------------------------------------

Commit 84e6d87b2de671fff1ddeaffb02003ef2ffd0b09 in couchdb-fauxton's branch refs/heads/master
from [~benkeen]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-fauxton.git;h=84e6d87 ]

Fix the flash on doc page route changes

This is subtle and only occurs on Chrome. To reproduce:
1. Go to the Database -> All Docs page for a database.
2. Click from the All Documents page to All Design Docs.

Click back and forth a few times. Notice that sometimes there's a
sort of quick flash that appears over the breadcrumbs section making
it look a little like the breadcrumbs are being re-rendered.

Closes COUCHDB-2467

> Minor flashing over breadcrumbs during route changes
> ----------------------------------------------------
>
>                 Key: COUCHDB-2467
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2467
>             Project: CouchDB
(Continue reading)

ASF GitHub Bot (JIRA | 24 Nov 18:28 2014
Picon

[jira] [Commented] (COUCHDB-2467) Minor flashing over breadcrumbs during route changes


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

ASF GitHub Bot commented on COUCHDB-2467:
-----------------------------------------

Github user benkeen closed the pull request at:

    https://github.com/apache/couchdb-fauxton/pull/155

> Minor flashing over breadcrumbs during route changes
> ----------------------------------------------------
>
>                 Key: COUCHDB-2467
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2467
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Ben Keen
>            Assignee: Ben Keen
>
> Neat CSS issue. After fixing COUCHDB-2465 I noticed the problem wasn't 100% fixed... There's a sort of
quick flashing that appears over the breadcrumbs section on the Database pages when changing routes.
> To reproduce: 
> 1. In Chrome (looks fine in FF), go to the Database -> All Docs page for a database.
> 2. Click from the All Documents page to All Design Docs.
> Note: it's subtle! And it only occurs on Chrome, not Firefox. Notice that there's a sort of quick white
(Continue reading)


Gmane