Hi, I guess you all are very busy with other stuff so sorry for introducing another topic here.
I would like to share my experience with Royale and that said I have to admit that for me it is still rough to work with Royale and so I wonder why. This is one reason that comes to my mind: The Royale MXML is much different from the Flex MXML, so I can't reuse Flex MXML knowledge and it needs several cycles until a UI is the way I want it. On the other hand, the Royale MXML is also different from pure HTML. So I can't reuse HTML knowledge. Often it is easier for me to build stuff in pure CSS3/HTML than using Royale MXML. One reason for this is that there are tons of HTML/CSS3 snippets out there that solve nearly any problem. But we can't use this stuff directly with Royale. So I wonder how we can improve the Royale developer experience and how we can benefit from all these HTML/CSS3 snippets and docs out there? One idea that comes to my mind is that something like a "Smart HTML" component set could help out of this dilemma. A component set that contains/maps all HTML elements including all existing attributes but that is also enriched by additional smart properties (e.g. 'dataProvider' for an HTML table). Moreover, it should be easy to apply standard CSS3 to any element in the same way as it works with pure HTML markup. Please enlight me if something like this is already implemented or leave some comments if you think this makes sense... or not. ;-) BTW: Of course, I am just talking about the HTML/JS target. Again, thanks for your time! Olaf -- Sent from: http://apache-royale-development.20373.n8.nabble.com/
