Hey Steve,
I also like the typedInputs, but I have some questions about there usage. Let's take the "button color" field for example. You would have two options in the typed input:
- a msg.xxxx option to specify the color in the input message (with e.g. 'set' as default value for xxxx).
- a color input field to specify the color in the config screen
However:
-
Both options need a different type of html input field: color or text. Is this possible? Because a lot of UI nodes will need to specify colors on their config screen...
-
I like the typedinput options because you immediately see where the color will be coming from. Because currently I always forget how the nodes work:
- Do they accept values from the input message only when no value has been specified in the config screen.
- Do they always accept values from the input message, even when a value has been specified in the config screen. In the latter case the value from the config screen, that can be overwritten by a value in the message.
With the typedInput options on the other hand, it is very clear where the value is coming from. However suppose you select the 'msg.xxx' option, is it then also possible to specify a 'default' color in the other non-selected color option?
Never heard of the word "badgering". And Google translate doesn't tell me if I should interpret this in a positive or negative way 
What is not clear to me yet: how do you specify the layout of a page? Is that via a layout tool, or do you need to enter manually this via a text editor, or ...
Are you referring here to your topic tree? Am I correct that this tree would have to solve our current message replay issues?
To understand your setup a bit better: so you have one big tree, where a.o. the config of all UI nodes is being stored. And that tree is stored on the backend or the frontend side? If it would be on the frontend side, then I don't understand how a new client would get automatically a copy of that tree...
