Hi Alex, >Welcome back.
Thank you! >Can you elaborate on how Royale MXML is different from Flex MXML Maybe I have exaggerated a bit when I said that we can't reuse Flex MXML knowledge. Of course, that basic principle is the same and some important attributes are also the same. So, yes, we can reuse this knowledge. I think the main problem (for me) is that it's not so easy to know which components are working well with which beads. And it's also not so easy to find a bead that solves a particular problem. What I am often doing is to copy and paste a bead to different parents and if nothing works I replace e.g. a container by a group or whatever and test it again. But each modification needs a compilation to check the results. And this is time-consuming. Maybe the Flex way is more intuitive. You can just pop-up the available component attributes by your IDE to check out what is there. If e.g. all attributes of a Flex component would be loosely coupled and available for tons of other components it would be a similar problem. Please don't get me wrong: I think I understand the beads concept and I don't want to say that it is bad, but it would be great to have the possibility to list all relevant beads for a particular component. (Maybe this is already there and I didn't realize it) > Snippet-pasting is easy Don't get me wrong, I don't want to say that we should be able to just copy and paste whatever snippet into our code. I tried to say that all these snippets out there are really helpful to solve your particular problem or they gives you new ideas of how to implement something. These tons of HTML/CSS3 snippets are similar to what we had in the Flex world years ago with all these tons of Flex blogs and docs. At the end an indispensable resource of ideas for solutions to problems. >Wrapping HTML/CSS/JS/SVG/WASM in components will allow our workflow to provide more and more information to our developers. That basically sounds like the right way... but I am not sure if it really works to have one component set that targets multiple platforms. What I am thinking of is to have different component sets, each specialized for a particular platform and regarding HTML by using all the stuff (elements/properties/selectors) which is already there in the HTML world. But I have to admit that I am still not sure by myself if this makes sense... Probably I also have to re-read your words a few times to make sure I got what you said ;-) Thank you!! Olaf -- Sent from: http://apache-royale-development.20373.n8.nabble.com/
