pepperdash/Essentials
1
0
Fork 0
mirror of https://github.com/PepperDash/Essentials.git synced 2026-01-11 19:44:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Removed .md from all links

hvolmer
2020-02-13 11:25:39 -07:00
parent dcca28bc32
commit 55213fefd0
6 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Arch-1.md

@@ -34,4 +34,4 @@ This flat structure ensures that every device in a system exists in one place an
![Architecture overview](https://pepperdash.github.io/Essentials/arch-overview.png) ![Architecture overview](https://pepperdash.github.io/Essentials/arch-overview.png)
Next: [Configurable lifecycle](Arch-lifecycle.md) Next: [Configurable lifecycle](Arch-lifecycle)

2
Get-started.md

@@ -22,4 +22,4 @@ To help understand Essentials Framework, we recommend starting with the current
1. Run the command `devmethods:1 display-1`. This will print the public methods available for the device with key "display-1". 1. Run the command `devmethods:1 display-1`. This will print the public methods available for the device with key "display-1".
1. Run the command `devjson:1 {"deviceKey":"display-1","methodName":"PowerOn", "params": []}`. This will call the method PowerOn() on the device with key "display-1". 1. Run the command `devjson:1 {"deviceKey":"display-1","methodName":"PowerOn", "params": []}`. This will call the method PowerOn() on the device with key "display-1".
Next: [Standalone use](Standalone-Use.md) Next: [Standalone use](Standalone-Use)

2
Home.md

@@ -62,4 +62,4 @@ The `master` branch always contain the latest stable version. The `development`
5. Create a Pull Request to pull your branch into the appropriate branch in the main repository. 5. Create a Pull Request to pull your branch into the appropriate branch in the main repository.
6. Your Pull Request will be reviewed by our team and evaluated for inclusion into the main repository. 6. Your Pull Request will be reviewed by our team and evaluated for inclusion into the main repository.
Next: [Get started](Get-started.md) Next: [Get started](Get-started)

2
SIMPL-Bridging.md

@@ -18,4 +18,4 @@ Some of the main advantages are:
2. You have a floor of conference rooms that all share some centralized hardware like DSP, AV Routing and a shared CEN-GWEXER gateway with multiple GLS-OIR-CSM-EX-BATT occupancy sensors. All the shared hardware can be defined in the Essentials configuration and bridged over an EISC to each program that needs access. The same device can even be exposed to multiple programs over different EISCs. 2. You have a floor of conference rooms that all share some centralized hardware like DSP, AV Routing and a shared CEN-GWEXER gateway with multiple GLS-OIR-CSM-EX-BATT occupancy sensors. All the shared hardware can be defined in the Essentials configuration and bridged over an EISC to each program that needs access. The same device can even be exposed to multiple programs over different EISCs.
3. You have a SIMPL program that works for many room types, but because some rooms have different models of processors than others (CP3/CP3N/AV3/PRO3/DMPS3 variants), you have to maintain several versions of the program, compiled for each processor model to maintain access to features like the System Monitor slot. You can use Essentials running in a slot on a processor to expose the System Monitor and many other features of the processor, regardless of model. Now you only need to maintain a single SIMPL program defined for your most complex processor application (ex. PRO3) 3. You have a SIMPL program that works for many room types, but because some rooms have different models of processors than others (CP3/CP3N/AV3/PRO3/DMPS3 variants), you have to maintain several versions of the program, compiled for each processor model to maintain access to features like the System Monitor slot. You can use Essentials running in a slot on a processor to expose the System Monitor and many other features of the processor, regardless of model. Now you only need to maintain a single SIMPL program defined for your most complex processor application (ex. PRO3)
Next: [Essentials architecture](Arch-summary.md) Next: [Essentials architecture](Arch-summary)

2
Standalone-Use.md

@@ -21,4 +21,4 @@ By defining devices and a room in a JSON configuration file, Essentials can cont
- Schedule awareness via Video Codec - Schedule awareness via Video Codec
- One button meeting join for Video Calling (with supported Video Codec) - One button meeting join for Video Calling (with supported Video Codec)
Next: [Simpl Windows bridging](SIMPL-Bridging.md) Next: [Simpl Windows bridging](SIMPL-Bridging)

8
_Sidebar.md

@@ -11,10 +11,10 @@
**Technical documentation** **Technical documentation**
* [Essentials Architecture](Arch-summary) * [Essentials Architecture](Arch-summary)
* [Devices and DeviceManager](Arch-1.md) * [Devices and DeviceManager](Arch-1)
* [Configurable lifecycle](Arch-lifecycle.md) * [Configurable lifecycle](Arch-lifecycle)
* [Activation phases](Arch-activate.md) * [Activation phases](Arch-activate)
* [More](Arch-topics.md) * [More](Arch-topics)
* [Plugins](Plugins) * [Plugins](Plugins)
* [Communication Basics](Communication-Basics) * [Communication Basics](Communication-Basics)
* [Debugging](Debugging) * [Debugging](Debugging)