|Re: Persisting WindowBuilder component properties as XML Elements in XWT [message #1446464 is a reply to message #1446028]
||Thu, 16 October 2014 22:19
| Konstantin Scheglov
Registered: July 2009
If I don't miss something, WindowBuilder does it because it is where XWT expects properties to be.|
So, XWT Designer (actually it was mainly done as a simple prototype of XML UIs support in WindowBuilder before implementing GWT UiBinder designer) uses org.eclipse.wb.internal.core.xml.model.property.XmlAttributeProperty, which updates element attributes.
Also, most of the properties are org.eclipse.wb.internal.core.xml.model.property.GenericPropertyImpl, and use org.eclipse.wb.internal.core.xml.model.property.accessor.ExpressionAccessor to actually update XML.
And org.eclipse.wb.internal.core.xml.model.property.accessor.ExpressionAccessor.setExpression(XmlObjectInfo, String) is also implemented to update attributes.
In theory you can add org.eclipse.wb.internal.core.xml.model.broadcast.GenericPropertySetExpression broadcast, so intercept setting expressions and create elements instead.
[Updated on: Thu, 16 October 2014 22:20]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01394 seconds