search

octoblu / issues

The place to report Octoblu issues
3 stars 2 forks source link

Designer: Message content browsing #246

Open brianehlert opened 8 years ago

brianehlert commented 8 years ago

when in the Designer and working with a Filter, compose, or some other node. If I can send a message to that node, it would make flow composition much easier if the keys and/or data from the message were shown in the message configuration of the Node.

For example: I add a filter node to a flow. I send a message to that flow. In the key field I am able to select the key to filter or dot source type the key name.

The requirement would be that a message would need to be sent for it to be known. But that would make the process more discoverable vs. having to capture the message as a debug and interpret it.

The end goal is to make it less developer-y

iamruinous commented 8 years ago

Making it easy to have message schemas would make this a lot better.

brianehlert commented 8 years ago

We need to show you what we have done with our WindowsNode. We have really taken advantage of the Schema possibilities. We even define defaults. What I describe here is different.

redaphid commented 8 years ago

This has been on my to-do list for a while. Max msp (https://cycling74.com) does this. Essentially detecting properties of messages going through nodes, so you can select them visually.

We haven't come up with a way of doing it yet that would be cost-effective in terms of time.

brianehlert commented 8 years ago

@iamruinous The issue with the message schema that we have discovered is that as we extend it, it really bogs down the designer. It appears that the designer parses the schema on every change on the page. So as I add more instances of a node to a flow the designer get slower and slower. This is a posted bug BTW.