Significant changes to use ReactJS extensively.

1. Replace the current layout library wcDocker with ReactJS based rc-dock. #6479
2. Have close buttons on individual panel tabs instead of common. #2821
3. Changes in the context menu on panel tabs - Add close, close all and close others menu items. #5394
4. Allow closing all the tabs, including SQL and Properties. #4733
5. Changes in docking behaviour of different tabs based on user requests and remove lock layout menu.
6. Fix an issue where the scroll position of panels was not remembered on Firefox. #2986
7. Reset layout now will not require page refresh and is done spontaneously.
8. Use the zustand store for storing preferences instead of plain JS objects. This will help reflecting preferences immediately.
9. The above fix incorrect format (no indent) of SQL stored functions/procedures. #6720
10. New version check is moved to an async request now instead of app start to improve startup performance.
11. Remove jQuery and Bootstrap completely.
12. Replace jasmine and karma test runner with jest. Migrate all the JS test cases to jest. This will save time in writing and debugging JS tests.
13. Other important code improvements and cleanup.

README.md

@@ -1,7 +1,7 @@
-# pgAdmin 4 
+# pgAdmin 4
 
 pgAdmin 4 is a rewrite of the popular pgAdmin3 management tool for the
-PostgreSQL (http://www.postgresql.org) database. 
+PostgreSQL (http://www.postgresql.org) database.
 
 In the following documentation and examples, *$PGADMIN4_SRC/* is used to denote
 the top-level directory of a copy of the pgAdmin source tree, either from a
@@ -9,9 +9,8 @@ tarball or a git checkout.
 
 ## Architecture
 
-pgAdmin 4 is written as a web application in Python, using jQuery and Bootstrap
-for the client side processing and UI. On the server side, Flask is being
-utilised.
+pgAdmin 4 is written as a web application with Python(Flask) on the server side
+and ReactJS, HTML5 with CSS for the client side processing and UI.
 
 Although developed using web technologies, pgAdmin 4 can be deployed either on
 a web server using a browser, or standalone on a workstation. The runtime/
@@ -22,7 +21,7 @@ which will execute the Python server and display the UI.
 
 To build the runtime, the following packages must be installed:
 
-* NodeJS 12+
+* NodeJS 16+
 * Yarn
 
 Change into the runtime directory, and run *yarn install*. This will install the
@@ -59,20 +58,20 @@ simple - adapt as required for your distribution:
    ```bash
    $ python3 -m venv venv
    ```
-   
+
 2. Now activate the virtual environment:
 
    ```bash
    $ source venv/bin/activate
    ```
-   
+
 3. Some of the components used by pgAdmin require a very recent version of *pip*,
    so update that to the latest:
-   
+
    ```bash
    $ pip install --upgrade pip
    ```
-   
+
 4. Ensure that a PostgreSQL installation's bin/ directory is in the path (so
    pg_config can be found for building psycopg3), and install the required
    packages:
@@ -80,20 +79,20 @@ simple - adapt as required for your distribution:
    ```bash
    (venv) $ PATH=$PATH:/usr/local/pgsql/bin pip install -r $PGADMIN4_SRC/requirements.txt
    ```
-   
+
    If you are planning to run the regression tests, you also need to install
    additional requirements from web/regression/requirements.txt:
 
    ```bash
    (venv) $ pip install -r $PGADMIN4_SRC/web/regression/requirements.txt
    ```
-   
+
 5. Create a local configuration file for pgAdmin. Edit
    $PGADMIN4_SRC/web/config_local.py and add any desired configuration options
    (use the config.py file as a reference - any settings duplicated in
    config_local.py will override those in config.py). A typical development
    configuration may look like:
-   
+
     ```python
     from config import *
 
@@ -126,7 +125,7 @@ simple - adapt as required for your distribution:
             'pgadmin4-server.db'
         )
    ```
-   
+
    This configuration allows easy switching between server and desktop modes
    for testing.
 
@@ -137,13 +136,13 @@ simple - adapt as required for your distribution:
    ```bash
    (venv) $ python3 $PGADMIN4_SRC/web/setup.py
    ```
-   
+
    or by starting pgAdmin 4:
 
    ```bash
    (venv) $ python3 $PGADMIN4_SRC/web/pgAdmin4.py
    ```
-   
+
    Whilst it is possible to automatically run setup in desktop mode by running
    the runtime, that will not work in server mode as the runtime doesn't allow
    command line interaction with the setup program.
@@ -228,7 +227,7 @@ To build a source tarball:
 (venv) $ make src
 ```
 
-To build a PIP Wheel, activate either a Python 3 virtual environment, configured 
+To build a PIP Wheel, activate either a Python 3 virtual environment, configured
 with all the required packages, and then run:
 
 ```bash
@@ -266,7 +265,7 @@ See https://www.pgadmin.org/support/ for support options.
 
 If you would like to report a security issue with pgAdmin, please email
 **security (at) pgadmin (dot) org**.
-    
+
 Note that this address should only be used for reporting security issues
 that you believe you've found in the design or code of pgAdmin, pgAgent,
 and the pgAdmin website. It should not be used to ask security questions.