Re: Acceptance of Royale by Flex Developers

and then ask for help when some API they need isn’t emulated. HTH, -Alex From: Carlos Rovira Date: Tuesday, October 8, 2019 at 11:59 AM To: "dev@royale.apache.org" Cc: Alex Harui Subject: Re: Acceptance of Royale by Flex Developers Hi I think we could remove one level or even

Re: Acceptance of Royale by Flex Developers

Hi I think we could remove one level or even two. Have at first level MIGRATE AN EXISTING APPLICATION (instead of inside CREATE AN APPLICATION ) then MIGRATE FROM FLEX

Re: Acceptance of Royale by Flex Developers

I'm going to try to address all of Chris Velevitch's several threads from today in this response. We have a page on Migrating Flex Apps here: https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html But it is hard to find (took me several clicks

Re: Acceptance of Royale by Flex Developers

Hi, I mean that like RO, that's a non visual component used to perform communications, we have other "components" or "code" that can be implemented as beads or strands. The concept behind is that Royale have the minimum code needed for functionality, and compose other parts (whatever the purpose

Re: Acceptance of Royale by Flex Developers

So you are suggesting a RemoteObject is a headless component who's base class only supports the model and controller plugins and that UI classes extend the headless component to add in the view? On Tue, 8 Oct 2019 at 15:52, Carlos Rovira wrote: > > Hi Chris, > > thanks for sharing your thoughts.

Re: Acceptance of Royale by Flex Developers

Hi Chris, thanks for sharing your thoughts. IMHO, not always a "strand" is a "visual component". This relation is not always true. a strand could be a non visual component (for example the implementation of RemoteObject in the Network library). And a bead could be a strand itself. I think the

Acceptance of Royale by Flex Developers

The use of the terms "strands" and "beads" still doesn't make sense to me because they are concepts I have never heard before and it is creating a barrier to acceptance and deepens the learning curve. As far as I can tell, it's something to do with visual/UI components. The section "Strands and