@5minds/node-red-dashboard-2-processcube-ui-page-navigation
Advanced tools
Comparing version 1.0.0 to 1.0.1
{ | ||
"name": "@5minds/node-red-dashboard-2-processcube-ui-page-navigation", | ||
"version": "1.0.0", | ||
"version": "1.0.1", | ||
"description": "A basic example of a third-party node that integrates with Node-RED Dashboard 2.0", | ||
@@ -5,0 +5,0 @@ "keywords": [ |
@@ -1,32 +0,8 @@ | ||
# Example Node for Node-RED Dashboard | ||
# ProcessCube UI Page Navigation | ||
This repository contains a Dashboard 2.0 UI node that listens to UI events on a specific page. | ||
This repository contains an example, third-party, node for the Node-RED Dashboard. | ||
## Installation and Usage | ||
To get started, clone this repository: | ||
```bash | ||
# if using HTTPS: | ||
git clone https://github.com/FlowFuse/node-red-dashboard-2-ui-example.git | ||
# if using SSH: | ||
git clone git@github.com:FlowFuse/node-red-dashboard-2-ui-example.git | ||
``` | ||
Then, you can install it's dependencies with: | ||
```bash | ||
npm install | ||
``` | ||
## Development with Dashboard 2.0 | ||
You can read our [contribution guide](https://dashboard.flowfuse.com/contributing/widgets/third-party.html) for details on developing your own Dashboard 2.0 integrations & widgets. | ||
This project is intended to be used as a starting point for creating your own custom nodes that can integrate directly with [Node-RED Dashboard 2.0](https://github.com/FlowFuse/flowforge-nr-dashboard). | ||
Note that if you're looking to contribute directly to Node-RED Dashboard 2.0, then use the examples already in the core repository to build on, as they are structured differently to external/third-party widgets. | ||
## Architecture | ||
All third-party (non-core) nodes for Node-RED Dashboard 2.0 are structured such that they extend the core `ui-template` node, and provide access such that you can define custom HTML, CSS, and JavaScript for your widget. | ||
To use this node, you need to install the Dashboard 2.0 plugin for Node-RED. | ||
After installing both packages, simply drag the node into your flow and specify the name of the page where you want to listen for events. |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
24875
9