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

On 11/24/17, 1:54 AM, "Olaf Krueger" wrote: > >> A DataGrid, IMO, is not a Table. > >I agree, but for simple things, I think a table is good enough. Yes, a Table is good enough, but a Royale version of a Table optimized for columnar display of data should always be more efficient. If you know y

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

Hi Hars, >I assume you remember this article I wrote? Yeah, but think I don't realize the fact that we're already able to apply CSS3 and handle native HTML selectors within Royale. I've just re-read your article and today I understand it a way better. My brain always needs many repetitions to un

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

Hi Olaf, I assume you remember this article I wrote? https://github.com/ok-at-github/flexjs-docs/wiki/Adapting-HTML-CSS-JS-project > On Nov 24, 2017, at 11:54 AM, Olaf Krueger wrote: > > Hi Alex, > >> Maybe you ca

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

Hi Alex, >Maybe you can create them, and then it would be interesting to see if there are other bugs or missing features that we need to deal with to make it work This sounds like a good idea and I guess it is feasible for me, I'll keep this in mind. > A DataGrid, IMO, is not a Table. I agre

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 try

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 simple, editable table/da

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

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

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 brow

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

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 n

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

I'd completely agree. It'd allow developer to solve his/her own problems (by re-using existing css/html snippets), instead of using the Royale forum to walk up the learning curve. New converts to Flex/Royale would find this more natural as well. > On November 22, 2017 at 3:28 AM Olaf Krueger w

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

>Can you maybe create a little MXML and AS3 project... Yes, good idea, I will do this... maybe while thinking about such an example it turns out that it doesn't make sense at the end ;-) Olaf -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

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

I like your reasoning. Can you maybe create a little MXML and AS3 project (pseudo code, obviously) that shows what you think a 'HTML friendly MXML/AS' file would look like? Thanks, EdB On Wed, Nov 22, 2017 at 12:28 PM, Olaf Krueger wrote: > Hi, > I guess you all are very busy with other stuf

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

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