{"action":"opened","issue":{"url":"https://api.github.com/repos/andrei-tatar/node-red-contrib-ui/issues/4","labels_url":"https://api.github.com/repos/andrei-tatar/node-red-contrib-ui/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/andrei-tatar/node-red-contrib-ui/issues/4/comments","events_url":"https://api.github.com/repos/andrei-tatar/node-red-contrib-ui/issues/4/events","html_url":"https://github.com/andrei-tatar/node-red-contrib-ui/issues/4","id":117019255,"number":4,"title":"Enhancement suggestions","user":{"login":"TotallyInformation","id":1591850,"avatar_url":"https://avatars.githubusercontent.com/u/1591850?v=3","gravatar_id":"","url":"https://api.github.com/users/TotallyInformation","html_url":"https://github.com/TotallyInformation","followers_url":"https://api.github.com/users/TotallyInformation/followers","following_url":"https://api.github.com/users/TotallyInformation/following{/other_user}","gists_url":"https://api.github.com/users/TotallyInformation/gists{/gist_id}","starred_url":"https://api.github.com/users/TotallyInformation/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/TotallyInformation/subscriptions","organizations_url":"https://api.github.com/users/TotallyInformation/orgs","repos_url":"https://api.github.com/users/TotallyInformation/repos","events_url":"https://api.github.com/users/TotallyInformation/events{/privacy}","received_events_url":"https://api.github.com/users/TotallyInformation/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-11-15T21:33:15Z","updated_at":"2015-11-15T21:33:15Z","closed_at":null,"body":"I've put these into the [Google group](https://groups.google.com/forum/#!topic/node-red/dcljG1d3VQQ) as well. I've not included the issues here, I've raised those in separate posts.\r\n\r\n- I know that Material Design is meant to be flat but I think the button is just TOO flat, it isn't at all clear that there is a button present - poor UI design. No point in having a button unless users understand it *is* a button.\r\n\r\n- Switch buttons - It would be great if there were some additional configuration options\r\n   - Such as being able to define the return values for the switch so that the output could be fed directly into a controller (e.g. \"On\"/\"Off\" or \"on\"/\"off\", etc.)\r\n\r\n- Have an input field for msg.topic on all nodes with output. By default pass-through nodes should pass the topic through but it is really helpful to be able to put your own topic in. Again, because this is widely used by things such as MQTT, it would enable the output to be sent directly to an MQTT node.\r\n\r\n   Because there is no msg.topic, debugging may also be hard, especially when chaining things together since any debug output can't identify the source (it would mean having to put a single debug node for every output).\r\n\r\n- For nodes that take an input msg:\r\n\r\n   - Allow overrides on the label and group fields from the input msg.\r\n\r\n     That way for example, you could connect a range of input MQTT messages (each has a topic) to a range of output messages without having to set up each separately. This should be possible since groups and elements appear dynamically. They would disappear of course on a page reload but that's OK.\r\n\r\n   - Allow more variables in the template. Perhaps just exposing the msg variable so that we could do something like, on a text output node for example:\r\n\r\n        ```Temperature: {{msg.payload.temperature}}, From: {{msg.topic}}``` \r\n\r\n   - Being able to set the \"value\" element from a specific msg variable would save some additional processing nodes. Let's say that the temperature was on the msg.payload as in the example above. In this case, the \"value\" input field in the node would be set to \"msg.payload.temperature\"\r\n\r\n- The nodes that take input and produce output (number, slider, switch) \r\n\r\n   - don't trigger output when a new input is provided, only when the user changes something. That seems inconsistent to me and personally I would much prefer to get output on any change so that automated and manual inputs produce the same output.\r\n\r\nHope at least some of these will be possible - I'll add any others as I think of them."}}