Mercurial > gemma
view client/README.md @ 1947:4235fa8f59d7
clien: pdf-gen: load logo externally; add prepare step
* Change the way how the logo to be placed in the pdf is loaded:
It can be configured in the `.env.localĀ“ file, otherwise a placeholder
will be loaded from the static assets. The placeholder has not been
placed in `assets` because it won't be needed if a real logo has
been specified and thus should not compiled in by default.
* Add a mechanism to do asynchronous preparations before rendering.
This is needed for the completeion of the Image() loading, but it also
shows how asynchronous preparational step can be added in principle.
* Disable the start button when the current rendering is in progress.
author | Bernhard Reiter <bernhard@intevation.de> |
---|---|
date | Tue, 22 Jan 2019 10:01:08 +0100 |
parents | 72d6fcb2147d |
children | b5619087e3e9 |
line wrap: on
line source
* Install dependencies * Install (`xgettext`) tool (e.g. for Debian xgettext (GNU gettext-tools) 0.19.8.1) * Javascript `yarn install` * Extend or overwrite configuration via `.env.local`-file ``` cp .env .env.local ```` Modify `.env.local` according to your needs. * Start Development servers * Javascript Run webpack-dev-server with `yarn serve` Hint: if you want to access the dev-server via a tunnel with hot reload, you'll may need to explicitely set the url the browser has to call with public. Example: ```sh ssh bern@ourdev.intevation.de -L 8180:localhost:8180 yarn serve --port 8180 --public http://localhost:8180 ``` * Build `yarn build` builds the production ready assets to `web` folder. * Build `yarn build-demo` sets the hg revision as a node env var and builds the production ready assets to `web` folder. * Translation * Extract Messages via `make makemessages` * Translations are converted via `make translations` which is executed automatically with yarn serve/build For more information see [developer documentation](./docs/developer.md) * Tests * Unit tests are started via `yarn test:unit` * e2e tests are started via `yarn test:e2e` Vue cli supports the Chrome selenium driver out of the box If you are interested in using the Firefox variant of the driver see [Vue CLI Plugin Docs](https://github.com/vuejs/vue-cli/tree/dev/packages/%40vue/cli-plugin-e2e-nightwatch) and see also [Nightwatch documentation](http://nightwatchjs.org/gettingstarted#geckodriver)