Many people seem to agree. Android also has taken this XML-layout model, although to wire up the events you will need to find the controls from the layout tree and add the relevant event listeners that you need.
The key, I think, is that it's much easier to write tools to display and edit such XML documents, so interface designers become relatively sane to write. Contrast, for instance, to the problem of parsing a (possibly) hand-edited source file and working out how the controls are laid out there, and then allowing editing of it. I think it's not going to happen.
Posted Oct 5, 2012 12:19 UTC (Fri) by man_ls (subscriber, #15091)
[Link]
Exactly, I thought grand-parent was pining for Android tools too. The upside is that the layout design tool uses Eclipse and so it is tightly integrated with your code. The biggest downside is exactly the same: a monolithic IDE is a bit hard to use for graphical designers, and these days it hurts a little bit when people drive me away from my vim. (Also when those damn kids get close to my lawn, and likewise when the weather changes, but so it is with age.)
The idea is cool though, and much easier to use than HTML content creation tools (like e.g. Coda + Chrome). Often it is easier to touch the underlying XML file than delve in the endless lists of attributes, and the visual interface can do weird things; but you get to see the results of the tinkering in almost real time, and both options (graphical and text editing) are available.