forked from maxwellhadley/node-red-contrib-ipc
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathipc.html
55 lines (50 loc) · 1.83 KB
/
ipc.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
<!--
Copyright 2016 Maxwell Hadley
Licensed under the BSD 2-clause license - see accompanying LICENSE file
-->
<!-- Edit dialog -->
<script type="text/x-red" data-template-name="IPC-in">
<div class="form-row">
<label for="node-input-path"><i class="fa fa-bolt"></i> Path</label>
<input type="text" id="node-input-path" placeholder="">
</div>
<div class="form-row">
<label for="node-input-topic"><i class="fa fa-tasks"></i> Topic</label>
<input type="text" id="node-input-topic" placeholder="Topic">
</div>
<div class="form-row">
<label for="node-input-name"><i class="fa fa-tag"></i> Name</label>
<input type="text" id="node-input-name" placeholder="Name">
</div>
</script>
<!-- Help text -->
<script type="text/x-red" data-help-name="IPC-in">
<p>Listens for communication from another process, using a UNIX-domain socket or (on Windows) a named pipe.
A message is generated for each line of text received.</p>
<p>The node listens at the specified path:</p>
<ul>
<li>On Unix & Linux, this is a filesystem location which must be writeable, and must not exist when the flow is deployed</li>
<li>On Windows, this is a named pipe, in the form <b>\\.\pipe\<i>pipename</i></b>, which must not exist when the flow is deployed</li>
</ul>
</script>
<!-- Register node type -->
<script type="text/javascript">
RED.nodes.registerType('IPC-in', {
category: 'input',
defaults: {
path: {value: '', required:true},
topic: {value: ''},
name: {value: ''}
},
color: "Silver",
inputs: 0,
outputs: 1,
icon: "ipc.png",
label: function() {
return this.name || "IPC";
},
labelStyle: function () {
return this.name ? "node_label_italic" : "";
}
});
</script>