2022-12-05 17:58:23 +00:00
# PiSCSI Web
2020-12-31 01:39:32 +00:00
2021-05-23 15:55:24 +00:00
## Setup local dev env
2020-12-31 01:39:32 +00:00
2021-05-23 15:55:24 +00:00
```bash
2022-02-02 04:51:51 +00:00
# Change to python/web/src
$ cd python/web
2021-05-23 15:55:24 +00:00
# Make a virtual env named venv
$ python3 -m venv venv
# Use that virtual env in this shell
$ source venv/bin/activate
# Install requirements
$ pip install -r requirements.txt
# Use mocks and a temp dir - start the web server
2022-02-02 04:51:51 +00:00
$ BASE_DIR=/tmp/images/ PATH=$PATH:`pwd`/mock/bin/ cd python/web & & PYTHON_COMMON_PATH=$(dirname $PWD)/common/src PYTHONPATH=$PWD/src:${PYTHON_COMMON_PATH} python3 src/web.py
2021-05-23 15:55:24 +00:00
```
### Mocks for local development
2021-10-06 01:39:26 +00:00
You may edit the files under `mock/bin` to simulate Linux command responses.
2022-12-05 17:58:23 +00:00
TODO: piscsi-web uses protobuf commands to send and receive data from piscsi.
2021-11-07 00:25:02 +00:00
A separate mocking solution will be needed for this interface.
2022-08-28 01:38:23 +00:00
## (Optional) Pushing to the Pi via git
This is a setup for pushing code changes from your local development environment to the Raspberry Pi without a roundtrip to the remote GitHub repository.
2021-05-23 15:55:24 +00:00
2022-12-05 17:58:23 +00:00
Setup a bare repo on the piscsi
2020-12-31 01:39:32 +00:00
```
2022-12-05 17:58:23 +00:00
$ ssh pi@piscsi
2021-05-23 15:55:24 +00:00
$ mkdir /home/pi/dev.git & & cd /home/pi/dev.git
$ git --bare init
Initialized empty Git repository in /home/pi/dev.git
2020-12-31 01:39:32 +00:00
```
2021-05-23 15:55:24 +00:00
Locally
```
2022-12-05 17:58:23 +00:00
$ cd ~/source/PISCSI
$ git remote add pi ssh://pi@piscsi/home/pi/dev.git
2021-05-23 15:55:24 +00:00
$ git push pi master
```
2021-12-26 21:36:12 +00:00
## Localizing the Web Interface
2022-08-26 00:57:44 +00:00
We use the Flask-Babel library and Flask/Jinja2 extension for internationalization (i18n).
2021-12-26 21:36:12 +00:00
2022-05-02 19:42:09 +00:00
It uses the 'pybabel' command line tool for extracting and compiling localizations. The Web Interface start script will automatically compile localizations upon launch.
2021-12-27 06:00:29 +00:00
Activate the Python venv in src/web/ to use it:
2021-12-28 20:08:48 +00:00
```
2022-02-02 04:51:51 +00:00
$ cd python/web
2021-12-27 06:00:29 +00:00
$ source venv/bin/activate
$ pybabel --help
2021-12-28 20:08:48 +00:00
```
2021-12-27 06:00:29 +00:00
2021-12-28 20:08:48 +00:00
To create a new localization, it needs to be added to the LANGAUGES constant in
2022-12-05 17:58:23 +00:00
web/settings.py. To localize messages coming from the PiSCSI backend, update also code in
raspberrypi/localizer.cpp in the PiSCSI C++ code.
2021-12-26 21:36:12 +00:00
2022-08-05 14:30:20 +00:00
Once this is done, it is time to localize the Python code. The below steps are derived from the [Flask-Babel documentation ](https://python-babel.github.io/flask-babel/index.html#translating-applications ).
2022-05-02 19:42:09 +00:00
First, generate the raw messages.pot file containing extracted strings.
```
2022-12-11 22:17:14 +00:00
$ pybabel extract -F babel.cfg -o messages.pot src
2022-05-02 19:42:09 +00:00
```
### Initialize a new localization
When adding a localization for a new language, initialize the directory structure. Replace 'xx' with the two character code for the language.
```
2022-08-05 14:30:20 +00:00
$ pybabel init -i messages.pot -d src/translations -l xx
2022-05-02 19:42:09 +00:00
```
2022-12-11 19:05:05 +00:00
### Update an existing localization
Tip: Use the script **translation_update.sh** in this dir to automatically extract strings, update existing localizations, and print translation statistics.
2022-05-02 19:42:09 +00:00
After strings have been added or changed in the code, update the existing localizations.
```
2022-12-11 19:05:05 +00:00
$ pybabel update -i messages.pot -d src/translations
2022-05-02 19:42:09 +00:00
```
2021-12-26 21:36:12 +00:00
2022-05-02 19:42:09 +00:00
Then edit the updated messages.po file for your language. Make sure to update fuzzy strings and translate new ones.
2021-12-27 06:00:29 +00:00
When you are ready to contribute new or updated localizations, use the same Gitflow Workflow as used for any code contributions to submit PRs against the develop branch.
2021-12-28 20:08:48 +00:00
### Working with PO files
See the [GNU gettext documentation ](https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html ) for an introduction to the PO file format.
We make heavy use of __python-format__ for formatting, for instance:
```
#: file_cmds.py:353
#, python-format
msgid "%(file_name)s downloaded to %(save_dir)s"
msgstr "Laddade ner %(file_name)s till %(save_dir)s"
```
There are also a few instances of formatting in JavaScript:
```
#: templates/index.html:381
msgid "Server responded with code: {{statusCode}}"
msgstr "Servern svarade med kod: {{statusCode}}"
```
And with html tags:
```
#: templates/index.html:304
#, python-format
msgid ""
"Emulates a SCSI DaynaPORT Ethernet Adapter. < a href = \"%(url)s \"> Host "
"drivers and configuration required< / a > ."
msgstr ""
"Emulerar en SCSI DaynaPORT ethernet-adapter. < a href = \"%(url)s \"> Kräver "
"drivrutiner och inställningar< / a > ."
```
2022-08-26 00:57:44 +00:00
### Contributing to the project
2022-12-05 17:58:23 +00:00
New or updated localizations are treated just like any other code change. See the [project README ](https://github.com/PiSCSI/piscsi/tree/master#how-do-i-contribute ) for further information.
2022-08-26 00:57:44 +00:00
2021-12-27 06:00:29 +00:00
### (Optional) See translation stats for a localization
Install the gettext package and use msgfmt to see the translation progress.
2021-12-28 20:08:48 +00:00
```
2021-12-27 06:00:29 +00:00
$ sudo apt install gettext
2022-02-02 04:51:51 +00:00
$ cd python/web/src
2021-12-27 06:00:29 +00:00
$ msgfmt --statistics translations/sv/LC_MESSAGES/messages.po
2021-12-27 21:21:06 +00:00
215 translated messages, 1 untranslated message.
2021-12-28 20:08:48 +00:00
```