Request: Editable Properties Bar

[knolleary]

@TotallyInformation

Personally, I would like to see a much simplified method for creating the edit panel without needing so much HMTL boilerplate and mixed jQuery JavaScript. That would be a great benefit.

@TotallyInformation Indeed - as I said earlier in this thread:

@knolleary

That's not to say we couldn't provide a better way to generate a node's edit dialog from a schema of some sort. That would be useful - and we already have the groundwork for that with the subflow property UI work.

It would likely have to be a 3.0 type feature - as any node that made use of it would not work at all in previous versions.

As for your other suggestions, if you have any more concrete suggestions to make, then please do so.

@TotallyInformation

For example, being able to tell if a property has changed from its last deployed setting would be extremely helpful.

You mention this as an example event... when would this event be triggered? We already have the nodes:changed event that is emitted whenever a node is edited (such as when the edit dialog is closed) - do you mean it would be helpful if that event included more details of what has changed?

@TotallyInformation

We also have property validation functions but they are triggered differently to when the UI itself is changed which is confusing.

That is true - the one function does do double duty. So are you saying you'd prefer a separate function for when the node is being edited versus when it has been imported?

@TotallyInformation

We also can't tell in a node's edit code when the node is initially displayed vs when you open the panel.

Do you mean in the oneditprepare function? No-one has asked to be able to do so, and I can't say I've ever come across a scenario where this is needed. If you have a specific use case where this would be useful that would help understand the requirement more.