@mxtommy/kip 3.9.0-beta.15 → 3.9.0-beta.16

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (38) hide show
  1. package/README.md +12 -49
  2. package/package.json +1 -1
  3. package/public/assets/svg/icons.svg +343 -39
  4. package/public/{chunk-JRXB4H3R.js → chunk-25PZU2O2.js} +1 -1
  5. package/public/{chunk-UYHYM4HU.js → chunk-2A7APCUX.js} +7 -7
  6. package/public/{chunk-7ROSR534.js → chunk-2LVIMPKK.js} +2 -2
  7. package/public/{chunk-L4UIO6KZ.js → chunk-3NNJBUG2.js} +3 -3
  8. package/public/{chunk-KH2LYQ34.js → chunk-3TEG54JB.js} +1 -1
  9. package/public/chunk-5GDQVRW5.js +1 -0
  10. package/public/{chunk-UE2C4S42.js → chunk-5KVBD33V.js} +1 -1
  11. package/public/{chunk-E44UUOOY.js → chunk-65ID7QUH.js} +1 -1
  12. package/public/chunk-CRI44YBB.js +1 -0
  13. package/public/chunk-CSR4FRGT.js +1 -0
  14. package/public/chunk-DVIUW3OC.js +2 -0
  15. package/public/{chunk-AWECVMCK.js → chunk-EQYME7LZ.js} +1 -1
  16. package/public/chunk-FYD5M4IT.js +16 -0
  17. package/public/{chunk-WQ6UD7J4.js → chunk-HECHZXLY.js} +1 -1
  18. package/public/chunk-JZ6SEETI.js +11 -0
  19. package/public/{chunk-4TXMPFLE.js → chunk-MZ4HV3HJ.js} +1 -1
  20. package/public/{chunk-5ZFD7GS7.js → chunk-NHAQWUX3.js} +1 -1
  21. package/public/{chunk-IQFEZZ5Q.js → chunk-RO6EAWVQ.js} +1 -1
  22. package/public/{chunk-SOVSVBLY.js → chunk-SZ2ILSI7.js} +1 -1
  23. package/public/{chunk-NMRNE6VS.js → chunk-TEJD7CAE.js} +1 -1
  24. package/public/chunk-TGXMWTBW.js +1 -0
  25. package/public/{chunk-3PHQNZHK.js → chunk-V5UALPYU.js} +3 -3
  26. package/public/chunk-VAOWYL36.js +1 -0
  27. package/public/index.html +1 -1
  28. package/public/main-BLOBFFNL.js +53 -0
  29. package/public/chunk-4BZUNPAS.js +0 -15
  30. package/public/chunk-A7JAKUEN.js +0 -2
  31. package/public/chunk-B2TLSQTS.js +0 -1
  32. package/public/chunk-BAGWY54D.js +0 -11
  33. package/public/chunk-DSUPPAGD.js +0 -1
  34. package/public/chunk-EURN6O7T.js +0 -1
  35. package/public/chunk-FI56NUZD.js +0 -2
  36. package/public/chunk-JGYVOFIW.js +0 -1
  37. package/public/chunk-PECKIPUO.js +0 -1
  38. package/public/main-IMSYBGZF.js +0 -53
package/README.md CHANGED
@@ -16,9 +16,20 @@ Key features include:
16
16
  - **Multiple User Profiles**: Tailor configurations for different roles, devices, or use cases.
17
17
  - **Cross-Device Compatibility**: Access KIP remotely on any device by navigating to `http://<Signal K Server URL>:<port>/@mxtommy/kip`.
18
18
 
19
+ Typical complementary components you may install (many are often bundled with Signal K distributions):
20
+
21
+ **Navigation & Charting**
22
+ - **Freeboard‑SK** – Multi‑station, web chart plotter dedicated to Signal K: routes, waypoints, charts, alarms, weather layers, and instrument overlays.
23
+
24
+ **Visual Flow / Automation**
25
+ - **Node‑RED** – Low‑code, flow‑based wiring of devices, APIs, online services, and custom logic (alert escalation, device control automation, data enrichment, protocol bridging).
26
+
27
+ **Data Storage & Analytics**
28
+ - **InfluxDB / other TSDB** – High‑resolution historical storage of sensor & performance metrics beyond what lightweight widget charts should retain.
29
+ - **Grafana** – Rich exploratory / comparative dashboards, ad‑hoc queries, alert rules on stored metrics, correlation across heterogeneous data sources.
30
+
19
31
  KIP is open-source under the MIT license, built by the community and 100% free. Join the community on Discord or contribute to the project on GitHub!
20
32
 
21
- ## Read the Help introduction How-to
22
33
  ## Read the Help introduction How-to
23
34
  Read the [Introduction](https://github.com/mxtommy/Kip/blob/master/src/assets/help-docs/welcome.md) help file.
24
35
 
@@ -123,32 +134,6 @@ For example, Signal K will notify KIP when a water depth or temperature sensor r
123
134
  ## Multiple User Profiles
124
135
  If you have different roles on board: captain, skipper, tactician, navigator, engineer—or simply different people with different needs, each can tailor KIP as they wish. The use of profiles also allows you to tie specific configuration arrangements to use cases or device form factors.
125
136
 
126
- ## Complementary Components
127
- Typical complementary components you may install (many are often bundled with Signal K distributions):
128
-
129
- **Navigation & Charting**
130
- - **Freeboard‑SK** – Multi‑station, web chart plotter dedicated to Signal K: routes, waypoints, charts, alarms, weather layers, and instrument overlays.
131
-
132
- **Visual Flow / Automation**
133
- - **Node‑RED** – Low‑code, flow‑based wiring of devices, APIs, online services, and custom logic (alert escalation, device control automation, data enrichment, protocol bridging).
134
-
135
- **Data Storage & Analytics**
136
- - **InfluxDB / other TSDB** – High‑resolution historical storage of sensor & performance metrics beyond what lightweight widget charts should retain.
137
- - **Grafana** – Rich exploratory / comparative dashboards, ad‑hoc queries, alert rules on stored metrics, correlation across heterogeneous data sources.
138
-
139
- ## Complementary Components
140
- Typical complementary components you may install (many are often bundled with Signal K distributions):
141
-
142
- **Navigation & Charting**
143
- - **Freeboard‑SK** – Multi‑station, web chart plotter dedicated to Signal K: routes, waypoints, charts, alarms, weather layers, and instrument overlays.
144
-
145
- **Visual Flow / Automation**
146
- - **Node‑RED** – Low‑code, flow‑based wiring of devices, APIs, online services, and custom logic (alert escalation, device control automation, data enrichment, protocol bridging).
147
-
148
- **Data Storage & Analytics**
149
- - **InfluxDB / other TSDB** – High‑resolution historical storage of sensor & performance metrics beyond what lightweight widget charts should retain.
150
- - **Grafana** – Rich exploratory / comparative dashboards, ad‑hoc queries, alert rules on stored metrics, correlation across heterogeneous data sources.
151
-
152
137
  # Connect, Share, and Support
153
138
  KIP has its own Discord Signal K channel for getting in touch. Join us at https://discord.gg/AMDYT2DQga
154
139
 
@@ -181,28 +166,6 @@ Keeping KIP focused preserves responsiveness (lower CPU / memory), reduces UI cl
181
166
 
182
167
  In short: use KIP to see & act on live sailing information; use the complementary tools to store it long‑term, analyze it deeply, automate decisions, or build advanced integrations.
183
168
 
184
- ## Project Scope
185
- What KIP IS about:
186
- - Real‑time presentation of vessel & environment data (navigation, performance, systems) pulled from Signal K.
187
- - Fast, legible, touchscreen‑friendly dashboards for underway decision making.
188
- - Configurable widgets (gauges, charts, timers, controls) tuned for sailing operations.
189
-
190
- What KIP deliberately IS NOT trying to become:
191
- - A full data lake / long‑term time‑series historian.
192
- - A general purpose automation / rules / orchestration engine.
193
- - A universal external web‑app embedding or mash‑up framework.
194
- - A low‑code integration hub for arbitrarily wiring protocols and services.
195
-
196
- Those domains already have excellent, specialized open‑source tools. Instead of re‑implementing them, KIP plays nicely alongside them within a Signal K based onboard stack.
197
-
198
- **Processing & Extensions**
199
- - **Signal K Plugins** – Domain‑specific enrichment (polars, performance calculations, derived environmental data, routing aids) published directly into the Signal K data model that KIP can then display.
200
-
201
- **Why this separation matters**
202
- Keeping KIP focused preserves responsiveness (lower CPU / memory), reduces UI clutter, and accelerates iteration on core sailing UX. Heavy analytics, complex workflow logic, and broad third‑party embedding stay where they are strongest—outside—but still feed KIP through the common Signal K data fabric.
203
-
204
- In short: use KIP to see & act on live sailing information; use the complementary tools to store it long‑term, analyze it deeply, automate decisions, or build advanced integrations.
205
-
206
169
  **Tools**
207
170
  Linux, Mac, RPi, or Windows dev platform supported
208
171
  1. Install the latest Node version (v16+, v18 recommended)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mxtommy/kip",
3
- "version": "3.9.0-beta.15",
3
+ "version": "3.9.0-beta.16",
4
4
  "description": "An advanced and versatile marine instrumentation package to display Signal K data.",
5
5
  "license": "MIT",
6
6
  "author": {