| 80 | | * Discussion: [http://lists.osgeo.org/pipermail/grass-dev/2014-March/067665.html GRASS GIS Web UI] |
| | 80 | |
| | 81 | This idea will consist in building a web application "WebGRASS" which allows to run GRASS modules on modern browsers. |
| | 82 | The user interface for WebGRASS will be built using [http://www.webtoolkit.eu/wt Wt] , Web Toolkit . |
| | 83 | WT provides C++ API and python bindings (available on [https://github.com/wdu/pywt github]) for developing web widgets, |
| | 84 | The main User Interface composed by : |
| | 85 | * Auth-module (user log-in) |
| | 86 | * mapset-location wizard |
| | 87 | * map canvas (based on openlayers) |
| | 88 | * toolbar with: |
| | 89 | - pan |
| | 90 | - query |
| | 91 | - zoom in - out - to bbox - to layer - to region |
| | 92 | - save to img mapcanvas |
| | 93 | - save display extent to region |
| | 94 | - menu bar with same layout of grass desktop |
| | 95 | * Command line prompt (a GRASS shell based on IPython Notebook) |
| | 96 | |
| | 97 | '''Security concerns''' |
| | 98 | |
| | 99 | By default Web-GRASS is designed to allow access to trusted users. |
| | 100 | Each user will be an UNIX user on the server with his own home. |
| | 101 | The web-grass UI interface will be accessible through an opportune registration/auth/login framework. |
| | 102 | The communication over the network will be encrypted using HTTPS. |
| | 103 | Will be choice of deployment team to decide to adopt any 'Extra security layer'. This can be achieved using tools like : |
| | 104 | * [https://www.docker.io/ docker] |
| | 105 | * [https://linuxcontainers.org/ lxc] |
| | 106 | * [http://supervisord.org/ supervisors] |
| | 107 | * [http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.cmds/doc/aixcmds5/ulimit.htm ulimit] |
| | 108 | |
| | 109 | |
| | 110 | Discussion on the GRASS-DEV mailing-list [http://lists.osgeo.org/pipermail/grass-dev/2014-March/067665.html GRASS GIS Web UI] |
