@@ -11,7 +11,7 @@ Each part have it's own `README.md` where all the information relative to the sa
## Installation
```shell
git clone git@github.com:PoCFrance/Elivia.git
git clone git@github.com:PoCInnovation/Elivia.git
```
You need [Android Studio](https://developer.android.com/studio) to build the frontend application. When you'll open the project, it will automatically sync all dependencies.
@@ -27,7 +27,7 @@ first start the back-end
cd back
go run ./
```
More information [here](https://github.com/PoCFrance/e/blob/master/back/README.md)
More information [here](https://github.com/PoCInnovation/Elivia/blob/master/back/README.md)
-**Frontend**
@@ -38,7 +38,7 @@ In the `Build` tab, select `Build Bundle(s) / APK(s)` and then `Build APK(s)`.
Once the build has finished, you can copy the apk to your smartphone and install it by opening it in your file explorer.
More information [here](https://github.com/PoCFrance/e/blob/master/front/README.md)
More information [here](https://github.com/PoCInnovation/Elivia/blob/master/front/README.md)
@@ -20,7 +20,7 @@ each of these language folder will hold a **response.json** and a **triggers.jso
## Code Architecture
For the moment only Go is supported, we may add a support for all language compiling to ELF.
Note that you can update the [loader](https://github.com/PoCFrance/e/blob/master/back/plugins/package.go) function to change the way the program load functions from external libraries
Note that you can update the [loader](https://github.com/PoCInnovation/Elivia/blob/master/back/plugins/package.go) function to change the way the program load functions from external libraries
Each Module will need an entry point, it been a function with this exact prototype
@@ -37,7 +37,7 @@ second : the **Map** you will be able to feed all the information you want to tr
## Triggers
This is where the majority of the configuration is. it define when and how the Module will be called. as well as the module itself
it is recommended to check the [sms](https://github.com/PoCFrance/e/blob/master/back/package/sms/res/locales/en/triggers.json) package as it serve as example.
it is recommended to check the [sms](https://github.com/PoCInnovation/Elivia/blob/master/back/package/sms/res/locales/en/triggers.json) package as it serve as example.
In this json, you will have an Array of Modules.
Each module is defined by an **Array** of **Module Type** thus, a module can be triggered by multiple ways, and have various catchphrase without having issues to define them all.
@@ -33,7 +33,7 @@ As said right before, the main part about Elia, is the IA, it was extracted from
One thing we added upon it, is the **package** system, Elia is able to load, compile, and train package at run time allowing you to add, remove or edit response at run time.
To say it briefly, its the bread and butter of Elia, you can format response and trigger, call your own function, and safely extract data from the sentences that triggered your package.
**Packages** seems complicated but they aren't that much of deal, really. Plus there is a full [documentation](https://github.com/PoCFrance/e/blob/master/back/PACKAGES.md) on how to write them, which features are implemented and the best practices around them.
**Packages** seems complicated but they aren't that much of deal, really. Plus there is a full [documentation](https://github.com/PoCInnovation/Elivia/blob/master/back/PACKAGES.md) on how to write them, which features are implemented and the best practices around them.