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
Copy file name to clipboardExpand all lines: readme.md
+29-25Lines changed: 29 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,39 +1,46 @@
1
-
## Runtime-Core
1
+
Runtime-Core
2
+
------------
3
+
4
+
[Release 0.1.0](release_notes_0.1.0.md)
2
5
3
6
### Setup Environment
4
-
On the first time you are cloning this repository, you need to run the command ```npm run init-setup```;
7
+
8
+
On the first time you are cloning this repository, you need to run the command `npm run init-setup`;
5
9
6
10
After running successfully this command you will have 2 folders (node_modules and vendor), these folders are excluded from the commit process, and are only for development.
7
11
8
-
if you already have the project configured on your machine, you only need run the command ```npm install``` to add new dependencies;
12
+
if you already have the project configured on your machine, you only need run the command `npm install` to add new dependencies;
9
13
10
14
if you have some trouble with the environment, you can open an issue;
11
15
12
16
### Javascript Environment
13
-
JavaScript code should be written in ES6.
14
-
There are direct dependencies from nodejs and npm, these can be installed separately or in conjunction with [nvm](https://github.com/creationix/nvm)
17
+
18
+
JavaScript code should be written in ES6. There are direct dependencies from nodejs and npm, these can be installed separately or in conjunction with [nvm](https://github.com/creationix/nvm)
15
19
16
20
#### dependencies:
17
-
* nodejs
18
-
* npm
19
-
* karma - Make the communication between unit test tool and jenkins. See more on [karma](http://karma-runner.github.io/0.13/index.html)
20
-
* mocha - Unit test tool. See more on [http://mochajs.org](http://mochajs.org/)
21
-
* jspm - Don't need compile the code, it uses babel (or traucer or typescript) to run ES6 code on browser. Know more in [jspm.io](http://jspm.io/)
22
-
* gulp - Automate and enhance your workflow. See more about gulp on [gulp](http://gulpjs.com/)
21
+
22
+
- nodejs
23
+
- npm
24
+
- karma - Make the communication between unit test tool and jenkins. See more on [karma](http://karma-runner.github.io/0.13/index.html)
25
+
- mocha - Unit test tool. See more on [http://mochajs.org](http://mochajs.org/)
26
+
- jspm - Don't need compile the code, it uses babel (or traucer or typescript) to run ES6 code on browser. Know more in [jspm.io](http://jspm.io/)
27
+
- gulp - Automate and enhance your workflow. See more about gulp on [gulp](http://gulpjs.com/)
23
28
24
29
#### Code Style and Hinting
30
+
25
31
On the root directory you will find **.jshintrc** and **.jscsrc**, these files are helpers to maintain syntax consistency, it signals syntax mistakes and makes the code equal for all developers.
1. if you will create a new repository, you can use this template, and can configure your development environment;
55
-
2. if you already have an respository cloned;
60
+
Verify these use cases: 1. if you will create a new repository, you can use this template, and can configure your development environment; 2. if you already have an respository cloned;
56
61
57
62
for both cases you just have run the command:
58
63
@@ -92,17 +97,16 @@ if you found some issues, please submit them into the respective repository;
92
97
---
93
98
94
99
### Karma
95
-
if you have some problems starting the karma tests, try running this commands for the following order:
This repository is ready to start working on development of runtime-core.
105
-
The code will go to the **src** folder.
106
-
The unit tests will be on **test** folder, following the name standard <component>.spec.js
109
+
110
+
This repository is ready to start working on development of runtime-core. The code will go to the **src** folder. The unit tests will be on **test** folder, following the name standard <component>.spec.js
107
111
108
112
The npm module **live-server** can be used for development tests, but it's not mandatory: [live-server](https://www.npmjs.com/package/live-server)
-[deploy Hyperty in the App Sandbox](https://github.com/reTHINK-project/core-framework/blob/master/docs/specs/runtime/dynamic-view/basics/deploy-hyperty.md)
-[exchange of messages between local Hyperties](https://github.com/reTHINK-project/core-framework/blob/master/docs/specs/runtime/dynamic-view/basics/intra-local-comm.md)
11
+
12
+
Known issues:
13
+
14
+
- no integration with Catalogue server
15
+
- no integration with Domain Registry Server
16
+
- Messages format not fully compliant with [WP2 Spec](https://github.com/reTHINK-project/architecture/tree/master/docs/datamodel/message).
17
+
- Hyperty descriptor and Protostub descriptor not fully compliant with [WP2 Spec](https://github.com/reTHINK-project/architecture/tree/master/docs/datamodel/hyperty-catalogue).
0 commit comments