From 8a683a858ed015f8f614f0d21c2e47f314c3eb2a Mon Sep 17 00:00:00 2001 From: Nick O'Leary Date: Sat, 4 Jul 2015 21:30:52 +0100 Subject: [PATCH] Created Design: Editor Events (markdown) --- Design:-Editor-Events.md | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 Design:-Editor-Events.md diff --git a/Design:-Editor-Events.md b/Design:-Editor-Events.md new file mode 100644 index 0000000..f755561 --- /dev/null +++ b/Design:-Editor-Events.md @@ -0,0 +1,10 @@ +The follow components emit events for the internal workings of the editor. Need to decide if it makes sense to expose these directly as part of the API, or hide them behind a single `RED.events` component. + +| Component | Event | Args | Description | +|-----------|-------|------|-------------| +|`RED.nodes` | `change` | `{ dirty: true/false }` | The 'dirty' state of the flow has changed.| +|`RED.sidebar` | `resize` | | The sidebar has changed size.| +|`RED.view` | `selection-changed` | `{ nodes: [], link: link }` | The node selection has changed. | +|`RED.workspaces` | `change` | `{ old: 'tab-id', workspace: 'tab-id' }` | The visible workspace tab has changed | + +