Custom categories.

[Michael Steenkamp]

Are there any plans on allowing users to configure categories themselves / is this something you guys would be interested in?

I'm thinking some kind of mapping could be defined in settings.js.

The use case being, we want to use default nodes but have our own specific categories.

[Nicholas O'Leary]

Nodes are free to use whatever category they want; the editor will automatically create category entries in the palette if one doesn't already exist.

The 'paletteCategories' option in settings.js can be used to defined what order categories appear in the palette - http://nodered.org/docs/configuration

Nick

This email, and any attachments, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. It is the property of Telogis, Inc. If you are not the intended recipient of this email, you are hereby notified that any dissemination, distribution or copying of this email, any attachments thereto, and use of the information contained, is strictly prohibited. If you have received this email in error, please notify the sender and permanently delete the original and any copy thereof.

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
For more options, visit https://groups.google.com/d/optout.

[Dave C-J]

But right now you can't allocate existing core nodes to other/new categories.

[Michael Steenkamp]

My question was more around putting existing nodes into new categories.
As an example, 

I feel like the function category is over populated and would like to move the csv/xml/json nodes into another 'parsers' category.

On Monday, August 15, 2016 at 8:01:33 PM UTC+12, Nick O'Leary wrote:

Nodes are free to use whatever category they want; the editor will automatically create category entries in the palette if one doesn't already exist.

The 'paletteCategories' option in settings.js can be used to defined what order categories appear in the palette - http://nodered.org/docs/configuration

Nick

On 15 August 2016 at 03:45, Michael Steenkamp <michael....@telogis.com> wrote:

Are there any plans on allowing users to configure categories themselves / is this something you guys would be interested in?

I'm thinking some kind of mapping could be defined in settings.js.

The use case being, we want to use default nodes but have our own specific categories.

This email, and any attachments, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. It is the property of Telogis, Inc. If you are not the intended recipient of this email, you are hereby notified that any dissemination, distribution or copying of this email, any attachments thereto, and use of the information contained, is strictly prohibited. If you have received this email in error, please notify the sender and permanently delete the original and any copy thereof.

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.