I don't think we have a list. Some components are just missing (no Menu/MenuBar). Some components are missing things (locked rows/columns, virtual renderers). I don't really know how to manage such a list. The Spark Button has over 100 public APIs. Tracking all of that would be daunting.
Some stuff may never happen (weak references). Some other stuff like PopUpManager can often just be done differently. Although if there is enough demand, we might create shims to ease migration pain. I know people would love it if Royale eventually had 1:1 parity with Flex, but that will take quite a while and I'm just not sure it is worth it. We have a different pattern under-the-hood in Royale in order to best ensure performance in production. IMO, it would be a mistake to make the port compilation easy but have the results not perform well enough. We've opted for requiring a bit more work in porting code in order to try to ensure adequate performance in production. So, from Alina's emails today, some documentation around popups is needed. We've seen that question several times already Maybe a FAQ? We've added some ASDoc tags in the Royale classes (@flexdocurl and @flexcomponent that could be added to a few more components that indicate what they can replace from Flex. But there isn't a reverse search. A volunteer could add that to the ASDoc app though. My 2 cents, -Alex On 2/6/18, 9:26 AM, "Andrew Wetmore" <[email protected]> wrote: >Do we have a list of Flex features not (yet) available in Royale, and >known >ways of getting to the desired result using Royale? Recent conversations >regarding Alina's product migration make me think that would be a useful >feature in the help documentation. > >a > >-- >Andrew Wetmore > >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14. >blogspot.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cab1132be823a4a9550a908 >d56d86b83a%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C636535347739075363 >&sdata=9GmPciqGZmuYdFrUz12LS%2FIkMACatH4VwrMoEzLllcA%3D&reserved=0
