Re: How to improve the Royale developer experience ("Smart HTML" component set)

Hi Olaf, As you try out various beads, you are doing the Royale form of snippet-pasting. In the future, if we add more metadata, we might even be able to tell you if a bead is compatible or not. That is unlikely to happen for folks pasting snippets into their HTML editor. But you if you are

Re: How to improve the Royale developer experience ("Smart HTML" component set)

Hi Olaf, Your MXML example is mostly possible with Royale today. In the HTML.swc are thin wrappers for most of the HTMLElements. I see there is a Td component, but there isn't a Table or Tr component. Maybe you can create them, and then it would be interesting to see if there are other bugs or

Re: How to improve the Royale developer experience ("Smart HTML" component set)

>Can these hang around for a while Yes, of course, there's no rush with this! There's more than enough other stuff that has to be done these days ;-) Thanks, Olaf -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: How to improve the Royale developer experience ("Smart HTML" component set)

Sweet! That looks great, thanks Olaf. Can these hang around for a while, until we're ready to give serious thought to an WASM compatible framework? Thanks, EdB On Thu, Nov 23, 2017 at 11:54 AM, Olaf Krueger wrote: > Hi Erik, > I've created an example that creates a

Re: How to improve the Royale developer experience ("Smart HTML" component set)

Hi Erik, I've created an example that creates a simple, editable table/datagrid. You can find the MXML pseudo code here (rows could be added by extending the data provider) [1]. This is a working HTML/CSS3 version (static rows) [2]. I think the key thing for me is to be able to use "built-in