On 2/25/16, 5:33 PM, "jude" <flexcapaci...@gmail.com> wrote:
>On Thu, Feb 25, 2016 at 9:24 AM, Alex Harui <aha...@adobe.com> wrote: >>But right now I am working on a component set that more closely matches >> the MX and Spark component APIs in order to lower the migration effort. >> However, just to get UIComponent to cross-compile, I have had to drag >>in a >> ton of ActionScript to be cross-compiled to JS so I am expecting a >> significant download size for this component set, but if that's what >> people want to use, well, then they can. >> > >How are you going to go about it? The advantage of drawing the components >yourself, rather than reuse DOM components is that the components look the >way you expect. The approach I'm taking is to get UIComponent to subclass the FlexJS UIBase instead of what it does now, so effectively, each UIComponent will end up being a Div. In theory, the Graphics object in the Div becomes an SVGElement. It is going to be heavy and big, but I think it will be worth the effort so we truly know how big it will be and how it will perform. It might help us convince everyone it is worth the migration pain of switching to the FlexJS Basic component set, or maybe it will be acceptable in size and performance for enough folks to remain an option, or maybe we'll discover that we can trade off a few things and find a more interesting midpoint. -Alex
