User:DolliejpffgslsydBearup

From Mariopedia

I can absolutely see that this (or sonmihteg similar) could be useful in some scenario's and I will keep an eye on this.. Always good to see some one trying out ideas and pushing things forward.I have some comments though: In your scenario it removes clear separation between the back-end service and the front-end client. The back-end service providing AML is deciding how it should be rendered, rather than providing data and allowing the client to decide how to render it. Fine in an entirely captive scenario but not entirely ideal or usual.Also, instead of creating an entirely new mark-up to learn, could you dynamically create the standard Android XML in you back-end service and create some kind of re-usable client in Android that would inflate this XML using LayoutInflaters to create views on the fly.Overall, I'm not sure I want to learn a new mark-up (and it will be a new mark-up because of all the Android nuances) for a reasonable niche scenario. Creating Android XML is not that painful most of the time and it is quite powerful once you understand it well. It is not that difficult to generate dynamic content as you can combine Android XML with code generated components.