Components are JS, so I don't think you can create a different component set that output more HTML.
Because they are JS, the only way I could think of having them do anything is to run JS that creates HTMLElements. This has the advantage that components that are added dynamically (later) via States or AS use the same code paths to add to the DOM as they do at startup. Also, many components are backed by more than one HTMLElement. Components are encapsulations of patterns. If you can show the pattern by which a component can result in HTML output instead of (or along with) JS output and that handles the kind of dynamic user experiences we want our users to build, write it up and we'll discuss it. There may be a way that works. Thanks, -Alex On 11/21/17, 1:32 PM, "Olaf Krueger" <m...@olafkrueger.net> wrote: >Hi, >I noticed that the compiler builds JS from MXML and the JS finally creates >the HTML elements dynamically at runtime. >I just wonder what is the benefit of this and if it would also possible to >introduce a component set that builds HTML from MXML directly. > > >Thanks, >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%7C6e60b2b63d8548d75 >fed08d531276987%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364689676972 >38655&sdata=g6SGAH0%2FIX4zlLaSZ1XUohI2OTkdKyt6Ewmirzz4EgA%3D&reserved=0
