pouchdb / pouchdb-fauxton Goto Github PK

See also pouchdb/pouchdb-fauxton-chrome-extension#4 , although you can reproduce it with just plain express-pouchdb/pouchdb-server too. Considering CouchDB's Fauxton isn't experiencing this problem, fixing #7 would probably fix this as well.

So basically I tried to do

git merge 9aafbd80e3a4545c292ca4c3251648fc0c80928a

But I found that there were too many merge conflicts. @NickColley, it seems that notably there are a lot of conflicts where you added branding colors to fauxton.less, but those styles were refactored out into new less files and so now we need to apply the changes over again. :(

Fauxton doesn't do strict modular CSS I'm going to document some of these instances, then we can build a styleguide of the most common components and start refactoring the UI.

Tabs

http://localhost:8000/#/activetasks

http://localhost:8000/#/database/_replicator/_changes

Buttons

http://localhost:8000/#database/newdatabase/compact

http://localhost:8000/#/replication

Outlined buttons

http://localhost:8000/#/_all_dbs

Popovers

Note the shadow/color differences here.

Forms

input[type="text"]

input[type="checkbox"]

input[type="radio"]

select

Will update as I go.

fauxton has been updated. Notably it now uses relative path which would allow it to work even when it is not mounted on the root with express-pouchdb (a recurring issue, c.f. pouchdb/pouchdb-server#260, pouchdb/pouchdb-server#256, pouchdb/pouchdb-server#183). It would be great to update it.
I tried to give it a quick look, but it seems the merge/copy mechanism is broken with recent versions. Unfortunately I run out of time and I'm not sure when I'll be able to come back on it.

I start following your instruction how to build Fauxton,

1. Copy repository
2. npm run prepublish

result:

Our links are hard to read etc, needs addressing.

I hosted pouch db on /db route using express-pouchdb
Then launching the Fauxton UI results in following errors.

The route should have been /db/_session.

At the moment we have to edit some core files to update fauxton, I'd like to discuss the steps it'd take to have a smoother upgrade path without having to manually rebase everytime.

In terms of the styling (less), I've pushed upstream a while a go the ability to set the brand colour, so we'd need to just have our own copy of variables.less and use that when we build.

There's a bit of markup (react) changes to add the logo. We could contribute upstream the ability to change this in a config file potentially?

I'd love to be in a position were we can make patches to pouchdb-fauxton and test them out in the pouchdb community then push them upstream with no conflicts.

Interested what you think @marten-de-vries 👍

Not sure if this is just me, the favicon supplied at the repo of the repo doesn't end up being used.

Right now the Fauxton subdirectories /js, /css, /img and /fonts are hung off the root. As per pouchdb/express-pouchdb#131 this brings up two main problems.

1. What if we are hosting the service somewhere other than that root? Such as /db/? The sub-directories are still only available off /img, /fonts, etc.
2. The sub-directory names are also legal DB names. So what if someone wants to create a db called fonts? It will collide with Fauxton.

I suspect the best solution is to hang these directories off _utils, where ever it is in the path. This clears both the namespace collision problem and the namespace invasion problem. However to make that work we both need to change the paths in express-pouchdb\index.js but we also need to change the index.html produced in couchdb-fauxton.

Just makes it easier to understand I think? Should be okay to do this?

It would be great to use this with ReactNative, there is only one small problem. It currently looks for window.PouchDB on the top thread, however it needs to use the debugger.js thread that the remote debugger runs in instead.