@gregoriusrippenstein/node-red-contrib-nodedev 0.2.9 → 0.3.1

package/README.md

@@ -1,8 +1,5 @@
 ## Node-RED nodes for the development of Node-RED nodes in Node-RED using Node-RED nodes.
 
-
-*** Work In Progress, not stable. ***
-
 *What?*
 
 The idea behind this collection of nodes to democratise the development of Node-RED nodes. Normally the development of your [own nodes](https://nodered.org/docs/creating-nodes/) will require the use of a third-party editor. Something like VSCode or Vim or Atom or god forbid, [Emacs](https://discourse.nodered.org/t/node-red-node-development-in-node-red/81525/2). This requirement makes creating nodes that much harder. So why not create nodes for Node-RED in Node-RED? After all, if you are using Node-RED, you probably understand how to use Node-RED.
@@ -24,6 +21,31 @@ This is not an inbuilt extension of Node-RED and obviously a more integrated wor
 
 It also gets more confusing since these nodes will open the Node-RED import dialog with pre-defined nodes. These are generally safe to import since that's how this package creates an initial set of nodes for representing a node package. Also importing nodes for an unknown node package is not recommended unless it happens to be your own package!
 
+### Motivation
+
+A comparison of Node-RED extensions and indirections
+
+| | Link Call |  Subflow | Link Nodes[^4] | Custom Node | Function node | Flow Tab |
+|:--|:--|:--|:--|:--|:--|:--|
+| Outputs [^1]  | =1 | >=1 | =1 | >=1 | >=1 | - |
+| Embeddable[^2] | Yes | Yes | - | Yes | Yes | Yes |
+| Modifiable[^3] | Yes | Yes | Yes | - | Yes | Yes |
+| Packages[^5] | - | -  | - | Yes | Yes | - |
+| Reusable[^6] | - | Yes | - | Yes | - | Yes |
+| Button[^7] | - | - | - | Yes | - | - |
+| Iconification[^8] | Yes | Yes | Yes | Yes | Yes | - |
+
+What this package does is make custom nodes modifiable within Node-RED.
+
+[^1]: Number of outputs definable. Subflows can have many outputs, link-call nodes only ever have one output. Zero outputs is possible for all extensions, one is standard and more than one is difficult.
+[^2]: Embeddable means with the functionality can be included in a flow.  Link-in/-out nodes redirect the flow of messages without those messages returning to the point where they left the original flow.
+[^3]: Does Node-RED provide support of modifying the extension? Node-RED does not provide any support for modifying custom nodes *within* Node-RED.
+[^4]: A combination of Link-in and Link-out nodes.
+[^5]: Can external NPMjs packages be included in the extension?
+[^6]: Is there a structured form of reusability for other flows? Subflows are structured to be reused, function nodes are not.
+[^7]: Can the extension be triggered with a button, i.e., as an inject node?
+[^8]: Can the icon be customised to make for simpler identification?
+
 ### Examples 
 
 Examples are included:

package/nodes/05-node-dev-ops.html

@@ -192,33 +192,37 @@
   <hr/>
   
   <div class="form-row">
-    <label for="node-input-pname" style="min-width: 170px;"><i class="fa fa-tag"></i> Package Name</label>
+    <label for="node-input-pname" style="min-width: 150px;">Package Details:</label>
+  </div>
+
+  <div class="form-row">
+    <label for="node-input-pname" style="min-width: 150px;"><i class="fa fa-tag"></i> Name</label>
     <input type="text" id="node-input-pname" placeholder="@username/node-red-contrib-somename"/>
   </div>
 
   <div class="form-row">
-    <label for="node-input-pversion" style="min-width: 170px;"><i class="fa fa-tag"></i> Package Version</label>
+    <label for="node-input-pversion" style="min-width: 150px;"><i class="fa fa-tag"></i> Version</label>
     <input type="text" id="node-input-pversion" placeholder="0.0.1"/>
   </div>
   
   <div class="form-row">
-    <label for="node-input-pauthorname" style="min-width: 170px;"><i class="fa fa-address-book-o"></i> Package Author Name</label>
+    <label for="node-input-pauthorname" style="min-width: 150px;"><i class="fa fa-address-book-o"></i> Author Name</label>
     <input type="text" id="node-input-pauthorname" placeholder="Alfred E. Neumann"/>
   </div>
 
   <div class="form-row">
-    <label for="node-input-pauthoremail" style="min-width: 170px;"><i class="fa fa-envelope-o"></i> Package Author Email</label>
+    <label for="node-input-pauthoremail" style="min-width: 150px;"><i class="fa fa-envelope-o"></i> Author Email</label>
     <input type="text" id="node-input-pauthoremail" placeholder="joe.blog@example.com"/>
   </div>
 
   <div class="form-row">
-    <label for="node-input-pdescription" style="min-width: 170px;"><i class="fa fa-book"></i> Package Description</label>
+    <label for="node-input-pdescription" style="min-width: 150px;"><i class="fa fa-book"></i> Description</label>
     <input type="text" id="node-input-pdescription" placeholder="Package description"/>
   </div>
 
   <div class="form-row">
-    <label for="node-input-ignore_package_check" style="min-width: 170px;"">
-      <span>Ignore package check?</span>
+    <label for="node-input-ignore_package_check" style="min-width: 150px;"">
+      <span>No package check?</span>
     </label>
     <input type="checkbox" id="node-input-ignore_package_check" style="display:inline-block; width:15px; vertical-align:baseline;">
   </div>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name" : "@gregoriusrippenstein/node-red-contrib-nodedev",
-  "version": "0.2.9",
+  "version": "0.3.1",
   "dependencies": {
     "pako":          "^2.1.0",
     "tar-stream":    "^3.1.6",