Browse Source

add structure

master
zeus 3 years ago
parent
commit
93a1610a29
  1. BIN
      poc-datacollector/modules/ROOT/images/intro.png
  2. BIN
      poc-datacollector/modules/ROOT/images/nvc.png
  3. BIN
      poc-datacollector/modules/ROOT/images/nvc1.png
  4. BIN
      poc-datacollector/modules/ROOT/images/vue-modules.png
  5. BIN
      poc-datacollector/modules/ROOT/images/vue.png
  6. 1
      poc-datacollector/modules/ROOT/nav.adoc
  7. 139
      poc-datacollector/modules/ROOT/pages/index-stucture.adoc

BIN
poc-datacollector/modules/ROOT/images/intro.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 70 KiB

BIN
poc-datacollector/modules/ROOT/images/nvc.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 24 KiB

BIN
poc-datacollector/modules/ROOT/images/nvc1.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.9 KiB

BIN
poc-datacollector/modules/ROOT/images/vue-modules.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 70 KiB

BIN
poc-datacollector/modules/ROOT/images/vue.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 70 KiB

1
poc-datacollector/modules/ROOT/nav.adoc

@ -1,2 +1,3 @@
* xref:index.adoc[datacollector] * xref:index.adoc[datacollector]
* xref:index-structure.adoc[project structure]
* xref:index-src.adoc[src-files] * xref:index-src.adoc[src-files]

139
poc-datacollector/modules/ROOT/pages/index-stucture.adoc

@ -0,0 +1,139 @@
= project structure and technologies used
image::ROOT:swarmlab-connect.png[float=right]
* (1) Opens the info menu
* (2) Run a shell in a running container
* (3) Opens web interface
* (4),(5) Source directory - Directory Maps
image::ROOT:types-of-mounts-bind.png[,250,float=right]
*"Directory Maps"* are the preferred mechanism for persisting data generated by and used by Docker containers. We use here "bind mounts" and they are dependent on the directory structure and OS of the host machine.
WARNING: Your local changes to the files will be overwritten by click on "Download" button. You should always *take a full backup* first (simple copy the directory tree)
== Vue.js (webclient)
[NOTE]
====
Vue.js is an open-source, progressive JavaScript framework for building user interfaces (UIs) and single-page applications.
====
*Library modularization* using a framework is common in frontend development.
What differentiates Vue.js from other alternatives is:
- its *“high decoupling”*,This means it is very simple to extend its functionalities as modules are included to an application. This means it is very simple to extend its functionalities as modules are included to an application.
For example, if we want to organize and render small visual components, all we need is Vue.js’s ‘core’ library.
It is not necessary to include additional libraries.
As the application grows,
- we have libraries to manage *routes* such as *‘vue-router’*,
- libraries to manage the global state such as *‘vuex’*
- and libraries to build responsive web applications such as *‘bootstrap-vue’*.
- Additionally, if our application needs to be optimized or needs good SEO, we can include the *‘vue-server-rendering’* library.
In the following figure, we can see how the libraries we just mentioned are progressively included, from a small SPA to multi-page applications (MPA).
image::ROOT:intro.png[intro]
TIP: The name of the framework – Vue – is the same phonetically in English as view, and it corresponds to the traditional Model-View-Controller (MVC) architecture
React and Angular are other Frameworks similar to vuejs
==== why Vue js
Below are the reasons stating why Vue js is gaining more popularity:
* Easy To Understand And Learn
* Easy Customization
* Readability And Single-file Components
* Lightweight
* Robust Tooling Ecosystem
* Flexibility And Integration Capabilities
* Much Advanced
* High Performance
* LAST BUT NOT LEAST, Documentation
==== Vuex
Vuex is a state management pattern + library for Vue.js applications.
- It serves as a centralized store for all the components in an application, with rules ensuring that the state can only be mutated in a predictable fashion.
- It also integrates with Vue's official devtools extension
to provide advanced features such as zero-config time-travel debugging and state snapshot export / import.
.What is a "State Management Pattern"?
[NOTE]
====
*Let's start with a simple Vue counter app:*
[source,javascript]
----
new Vue({
// state
data () { // <1>
return {
count: 0
}
},
// view
template: ` // <2>
<div>{{ count }}</div>
`,
// actions
methods: { // <3>
increment () {
this.count++
}
}
})
----
<1> The state, the source of truth that drives our app;
<2> The view, a declarative mapping of the state;
<3> The actions, the possible ways the state could change in reaction to user inputs from the view.
This is a simple representation of the concept of "one-way data flow":
====
image::ROOT:vue-modules.png[float=right]
image::ROOT:mvc.png[float=right]
image::ROOT:mvc1.png[float=right]
TIP: https://scrimba.com/learn/vuex[Online Vuex cources^]
==== Using Axios to Consume APIs
TIP: Axios is a library for http communication, making ajax requests, and so on.
https://github.com/axios/axios[See more^]
==== Using socket.io to Consume Websocket
Socket.IO aims to make realtime apps possible in every browser and mobile device, blurring the differences between the different transport mechanisms. It supports multiple transports, such as WebSockets, Flash sockets, long polling and more, automatically falling back when a transport fails
https://socket.io/[See more info here: Socket.io^]
Vue Packages
- https://www.npmjs.com/package/vue-socket.io-extended[socket.io client^]
- https://www.npmjs.com/package/vue-socket.io[socket.io]
Loading…
Cancel
Save