The Essentials Application Framework Libraries
Find a file
Andrew Welker ddb1f254e6 renamed room -> rooms
started on Dual Display room;
2020-06-30 00:34:24 -06:00
.github update workflows for name change 2020-06-17 12:10:12 -06:00
docs Merge pull request #10 from PepperDash/hotfix/ndorin-cleanout-unused-classes 2020-02-12 16:47:32 -07:00
essentials-framework renamed room -> rooms 2020-06-30 00:34:24 -06:00
Essentials-Template-UI@8eaf88791b Adds Template UI submodule 2020-04-23 09:55:33 -06:00
IR Drivers Updates DisplayControllerBridge to support BasicIrDisplay types, adds Samsung IR driver file, updates SetupFileSystem in ControlSystem.cs to build plugin folder 2019-06-24 15:16:20 -06:00
PepperDashEssentials renamed room -> rooms 2020-06-30 00:34:24 -06:00
Sample Presets DM Mods 2017-03-03 14:42:20 -07:00
.gitignore Updates comment and removes .json extension 2020-03-20 09:47:26 -06:00
.gitmodules Adds Template UI submodule 2020-04-23 09:55:33 -06:00
CONTRIBUTING.md Update CONTRIBUTING.md 2020-02-19 12:41:48 -07:00
devjson commands.json Insignificant changes to trigger build pipeline 2020-03-09 16:52:18 -06:00
LICENSE.md Updates LICENSE.md 2020-02-05 15:32:51 -07:00
PepperDashEssentials.sln Updates the name for Essentials_DM to PepperDash_Essentials_DM to ensure the .cplz name matches the .dll name 2020-04-01 15:08:24 -06:00
README.md Adds latest release link 2020-06-17 22:15:01 -06:00

PepperDash Essentials Framework (c) 2020

Latest Release

License

Provided under MIT license

Overview

PepperDash Essentials is an open source Crestron framework that can be configured as a standalone program capable of running a wide variety of system designs and can also be utilized as a plug-in architecture to augment other Simpl# Pro and Simpl Windows programs.

Essentials Framework is a collection of C# / Simpl# Pro libraries that can be utilized in several different manners. It is currently operating as a 100% configuration-driven system, and can be extended to add different workflows and behaviors, either through the addition of further device "types" or via the plug-in mechanism. The framework is a collection of "things" that are all related and interconnected, but in general do not have dependencies on each other.

Minimum Requirements

  • Essentials Framework runs on any Crestron 3-series processor, 4-series processor or Crestron's VC-4 platform.
  • To edit and compile the source, Microsoft Visual Studio 2008 Professional with SP1 is required.
  • Crestron's Simpl# Plugin is also required (must be obtained from Crestron).

Dependencies

The PepperDash.Core SIMPL# library is required. It is referenced as a submodule and will be automatically checked out when cloning this repo if set to recurse submodules. This allows different builds of the PepperDash.Core library to be referenced by checking out the desired submodule commit.

Utilization

Essentials was originally conceptualized as a standalone application for running control system logic entirely in Simpl# Pro. It is primarily designed around accomplishing this goal, but during development, it became obvious that it could easily be leveraged to also serve as a partner application to one or more SIMPL Windows programs.

Utilization of Essentials Framework falls into the following categories:

  1. Standalone Control System Application for controlling one or more rooms. See Standalone Use

  2. Partner Application to a SIMPL Windows program. This allows for several useful advantages. See SIMPL Windows Bridging

  • Dynamic device instantiation. Devices can be defined in configuration and instantiated at runtime and then bridged to a SIMPL Windows program via EISC.

  • Advanced logic. Some logic operations that cannot be affectively accomplished in SIMPL Windows (ex. JSON/XML serialization/deserialization, database operations, etc.) can be done in the Simpl# Pro environment and the necessary input and output bridged to a SIMPL Windows program via EISC.

  1. Hybrid Application that may contain elements of both standalone control and SIMPL partner application integration.
  • There may be a use case where a device can only be defined in a single application, but that device may need to be interacted with from multiple applications. The device can be defined in an Essentials application, interacted with in that application and also bridged to one or more SIMPL Windows applications.

Documentation

For detailed documentation, see the Wiki.

How-To (Getting Started)

See Getting Started