AEON Dashboard issueshttps://scm.atosresearch.eu/ari/aeon-dashboard/-/issues2019-01-11T19:29:00Zhttps://scm.atosresearch.eu/ari/aeon-dashboard/-/issues/14Automatize the creation of live demo resources2019-01-11T19:29:00ZJosé Gato LuisAutomatize the creation of live demo resourcesNow the live demo needs to be configured with a pre-configured channel. This is not possible first time of deployment, so adds a manual step after installation. We should improve this, with the creation of the channel during first deploy...Now the live demo needs to be configured with a pre-configured channel. This is not possible first time of deployment, so adds a manual step after installation. We should improve this, with the creation of the channel during first deploymenet automatically.
Related to #2AEON 0.4.0https://scm.atosresearch.eu/ari/aeon-dashboard/-/issues/9Crashin first time it runs2019-01-11T19:29:00ZJosé Gato LuisCrashin first time it runsmaybe only when SSL enabled:
```
GET /app/index.html Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0
events.js:160
throw er; // Unhandled 'error' event
^
Error: write after end
at S...maybe only when SSL enabled:
```
GET /app/index.html Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0
events.js:160
throw er; // Unhandled 'error' event
^
Error: write after end
at ServerResponse.OutgoingMessage.write (_http_outgoing.js:441:15)
at StaticServlet.writeDirectoryIndex_ (/usr/src/aeon-dashboard/scripts/web-server.js:272:9)
at /usr/src/aeon-dashboard/scripts/web-server.js:257:33
at FSReqWrap.oncomplete (fs.js:123:15)
```
AEON 0.4.0José Gato LuisJosé Gato Luishttps://scm.atosresearch.eu/ari/aeon-dashboard/-/issues/3WebApp Performance2019-01-11T19:29:00ZJavier Garcia HernandezWebApp PerformanceOur colleague @francisco.calle reported us about not good performance in the web according to the test pingdom.
The resulting time is around 1.5 and 2s and there are several weak points that could be improved: paralizations, caches, o...Our colleague @francisco.calle reported us about not good performance in the web according to the test pingdom.
The resulting time is around 1.5 and 2s and there are several weak points that could be improved: paralizations, caches, or even the size of some images.
It will be great to play with this tool. So, we will learnt how to make a better usage of Javascript and also to improve AEON webapp performance.AEON 0.4.0https://scm.atosresearch.eu/ari/aeon-dashboard/-/issues/1Running webapps in background of mobile devices2019-01-11T19:29:00ZJavier Garcia HernandezRunning webapps in background of mobile devicesWhy do we need that?
Imagine a web application showing locations in a map. This works perfectly in your desktop browser. For example in Android, if you dont have the browser in foreground the process is "sleeping". Android manage mult...Why do we need that?
Imagine a web application showing locations in a map. This works perfectly in your desktop browser. For example in Android, if you dont have the browser in foreground the process is "sleeping". Android manage multitasking using services, but this is a native functionality that you cannot access from a JS Webapp.
it seems we have some progresses in this topic that we should study some day. There are some new specifications to allow notifications out of the broswer to do the notifications native to the OS
https://notifications.spec.whatwg.org/
Together with web workers:
http://caniuse.com/#feat=webworkers
Could be an excellent way to make web applications, that in mobile devices could be working in background, making notifications integrated in the native system (like android).
A great example about that ideas:
http://updates.html5rocks.com/2015/03/push-notificatons-on-the-open-web?utm_source=twitterfeed&utm_medium=twitter&utm_campaign=Feed%3A+html5rocks+%28HTML5+Rocks%29
but the use GCM to publish/subscribe. We have to see how to do this with AEON. Very interesting, and something to study!!!