Versus,
We are about to start a story to persist the Tabs and History. Since
pgAdmin 4 is centered around the tree we need to be able to persist this
first.
If you are interested in making the changes suggested above we have some
additional work to do, otherwise we'd be happy to pick this up and
Hello,
In order to save everything in the backend sqlite database, maybe a jQuery
plugin needs to be developed that has the same interface as jStorage and
that will do Ajax calls instead of using the Local Storage.
The only caveat for this is that it needs to be registered in window.
$.jStorage in
Hi
This would be a welcome feature addition, but why not store the treeview
state in the configuration database? I'd prefer not to add another storage
mechanism without a very compelling reason.
If you need info on how it works, please feel free to ask questions.
Thanks.
On Tue, Jul 18, 2017 at
---
web/pgadmin/browser/__init__.py| 13 +-
.../browser/static/vendor/jStorage/jstorage.js | 996 +
.../browser/static/vendor/jStorage/jstorage.min.js | 16 +
.../browser/templates/browser/js/browser.js| 6 +-
4 files changed, 1029 insertions
This will restore tree structure on load like in good old pgadmin3.
