You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -28,10 +28,22 @@ If you are interested in **using** EVT to prepare an edition right away, you sho
28
28
If, on the other hand, you are interested in **developing** a specific functionality in EVT, or in modifying an existing one, or preparing your edition with the most recent (yet stable) version of EVT, you should download the [*GitHub Development framework*](https://github.com/evt-project/evt-viewer). See the *Development framework installation and use* section to know how to install and configure the environment needed for this purpose. If you intend to change the source code for personal needs, please **fork** the project. If you want to contribute to the main project (by fixing a bug or adding a feature), please ask for a **pull request** and/or contact us at evt.developers@gmail.com.
29
29
30
30
### 2.1 - Installation and use
31
-
Work in progress... stay in touch!
31
+
EVT 3 can be used to prepare an edition right away, immediately after downloading the release package on your hard drive: see the [Installation and management of the edition data](https://github.com/evt-project/evt-viewer-angular/wiki/Installation-and-use#installation-and-management-of-the-edition-data) section of the Wiki first, then [Configuration](https://github.com/evt-project/evt-viewer-angular/wiki/Configuration), to understand how EVT works and how you can use it to publish your editions.
32
+
33
+
If, on the other hand, you are interested in developing a specific functionality in EVT 3, or in modifying an existing one, we suggest that you clone the project as it is. The README.md explains how to install and configure the development environment needed for this purpose. This step is only needed if you want to start working with EVT source code, so it is in no way necessary for basic users. See [Development](https://github.com/evt-project/evt-viewer-angular/wiki/Development) section and subsections of the Wiki for further information on development guidelines.
34
+
35
+
32
36
33
37
### 2.2 - Configuration
34
-
Work in progress... stay in touch!
38
+
There are several configuration options, ranging from setting the folders where edition data is stored to choosing the User Interface layout and the tools to be made available for the final user, that can be set by editing the configuration files in the `assets/config` directory. To facilitate the configuration work, configuration options are divided into three macro groups:
39
+
40
+
* Edition Configuration (`edition_config.json`), where to set the configurations closely related to the digital edition, such as the title, the edition level(s), etc. [See details in the Wiki page](https://github.com/evt-project/evt-viewer-angular/wiki/Edition-Configuration).
41
+
* File Configuration (`file_config.json`), where to set the path(s) to the file(s) of the digital edition. [See details in the Wiki page](https://github.com/evt-project/evt-viewer-angular/wiki/File-Configuration).
42
+
* UI Configuration (`ui_config.json`), where to set the configuration closely related to the UI, such as the default language, the default/available theme(s), etc. [See details in the Wiki page](https://github.com/evt-project/evt-viewer-angular/wiki/Ui-Configuration).
43
+
44
+
It is also possible to configurate the style of editorial phenomena (e.g. addition, deletion, etc), in order to override the EVT default layouts. This particular configuration should be defined in the file `editorial_conventions_config.json`. [See details in the Wiki page](https://github.com/evt-project/evt-viewer-angular/wiki/Editorial-Conventions-Configuration)
45
+
46
+
For more information please refer to the [Configuration section](https://github.com/evt-project/evt-viewer-angular/wiki/Configuration) on the Wiki.
35
47
36
48
37
49
3 - Development framework installation and use
@@ -45,13 +57,13 @@ For development, you will only need Node.js installed on your environement. And
45
57
### 3.2 - Node
46
58
[Node](http://nodejs.org/) is really easy to install & now include [NPM](https://npmjs.org/).
47
59
You should be able to run the following command after the installation procedure
48
-
below.
60
+
below. To properly install all the dependency, please use 12.20.x/14.15.x/16.10.x or later minor version of NodeJS.
If nothing happens, then open your browser and navigate to `http://localhost:4200/`.
77
+
If nothing happens, then open your browser and navigate to `http://localhost:4205/`.
66
78
The app will automatically reload if you change any of the source files.
67
79
68
-
With the second instruction you can choose the port where to run the application (es `ng serve --port=4202`, thenn connecto to `http://localhost:4202/`).
80
+
If you want to use a different port where to run the application you can run `npm run ng serve -- --port=4200`, then connecto to `http://localhost:4200/`).
69
81
70
82
### 3.5 - Code scaffolding
71
83
@@ -229,21 +241,16 @@ They are defined respectively in the files below:
229
241
230
242
To use them, please refer to official scss documentation.
231
243
232
-
5 - EVT Configuration
244
+
5 - EVT Configuration: technical details
233
245
---------------------
234
-
There are several configuration options, ranging from the folders where edition data is stored to User Interface layout and available tools, that can be set by editing the configuration files that you can find in the `assets/config` directory.
235
-
To facilitate the configuration work, configuration options are divided into three macro group:
236
-
* Edition Configuration (`edition_config.json`), where to set the configurations closely related to the digital edition, such as the title, the edition level(s), etc.
237
-
* File Configuration (`file_config.json`), where to set the path(s) to the file(s) of the digital edition.
238
-
* Ui Configuration (`ui_config.json`), where to set the configuration closely related to the UI, such as the default language, the default/available theme(s), etc.
239
-
240
246
Configurations is defined as a `AppConfig` provider and is injected into main app module. It is loaded during app initialization, to that it will be immediately available for every component.
241
-
The three groups are gathered (although kept divided) in a single `EVTConfig` object.
247
+
The four groups are gathered (although kept divided) in a single `EVTConfig` object.
242
248
```
243
249
interface EVTConfig {
244
250
ui: UiConfig;
245
251
edition: EditionConfig;
246
252
files: FileConfig;
253
+
editorialConventions: EditorialConventionsConfig;
247
254
}
248
255
```
249
256
If you want to use a parameter from configuration in your component, you just need to import `AppConfig` and directly use its properties:
@@ -262,23 +269,14 @@ export class MyComponent {
262
269
}
263
270
```
264
271
265
-
### 5.1 - Edition Configuration
266
-
* `title: string;`, the main title of the digital edition. If you want to allow the translation of the title, use the proper key of the locale json file. If you leave it blank the default 'EVT Viewer' title will be shown.
267
-
* `\\ [...] `
268
-
269
-
### 5.2 - File Configuration
270
-
* `editionUrls: string[];`, list of paths to file(s) of your encoded edition. It can point either to an internal folder or to an external online resource.
271
-
* `\\ [...] `
272
-
273
-
### 5.3 - UI Configuration
274
-
* `localization: boolean;`, whether to have localization buttons to allow language change at runtime
275
-
* `defaultLocalization: string;`, the code of the default language to be used
276
-
* `\\ [...] `
272
+
If you want to add a parameter in configuration, you need to add it first to the interface of the specific group, indicating the exact type of data you expect for it.
277
273
278
274
6 - EVT Manual
279
275
---------------------
280
276
281
-
Work in progress... stay in touch!
277
+
As a user manual please refer to the [Wiki](https://github.com/evt-project/evt-viewer-angular/wiki). It will always be updated based on the features merged into the `develop` branch.
278
+
279
+
For the functionalities and instructions related to a specific release, it is possible to refer to the `evt-documentation.pdf` file inside the `doc` folder in the release package.
0 commit comments