Hi Olaf, Welcome back. Can you elaborate on how Royale MXML is different from Flex MXML? Is it just the component and attribute names? Or something else?
When you first learned Flex, you didn't know Flex MXML and somehow still found it easy to use. Regarding re-use of HTML/CSS snippets, I'm not sure we want to go make it so that you can copy/paste these snippets. We might be able to get that to work, but as soon as you need JS (or SVG or WASM) it will be much harder to make that work. Instead, IMO, the goal for Royale is to encapsulate these snippets (which can include JS, SVG and maybe even WASM) into components so that Royale users don't hit the problems these snippets solve in the first place, so that they can declaratively use these snippets, and so that we can provide developer assistance in the discovery and management of these snippets as components. Another way to think of it is that we aren't here to be another HTML/CSS editor, we are here to change the web development workflow to be more like traditional application development by adding tooling and structure in a way that scales to building enterprise-class, mission-critical applications. A report I read many years ago said that tons of web pages are successfully created by snippet-pasting, but a significant number of them throw exceptions that the browser simply tolerates and visitors don't see if they don't have their console open. Snippet-pasting is easy: you paste it, run it, undo it if it doesn't work, go get another snippet if you need to. But because of how JS works in the browser, you don't have to care about side-effects if they aren't noticed by your users. We want to allow that in the form of adding and removing MXML tags, but we also want to tell you about exceptions, side-effects, etc, because we want to make sure we help our developers create a foundation for an application that scales. Wrapping HTML/CSS/JS/SVG/WASM in components will allow our workflow to provide more and more information to our developers. Maybe not tomorrow, but in the future. A snippet can't know what other snippets it got pasted next to, but a component can tell what other components are in the same app. My 2 cents, -Alex On 11/22/17, 3:28 AM, "Olaf Krueger" <[email protected]> wrote: >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: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy >ale-development.20373.n8.nabble.com%2F&data=02%7C01%7C%7Cf47e9663645543041 >25008d5319c25db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364694690804 >81701&sdata=F2Ugk6YuhvZ%2B51zCzuRlfLdsEZMHwOGAZTs0DRc7AXI%3D&reserved=0
