On 3/5/17, 10:11 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> How will we achieve parity on the SWF side? And keep the SWF >> implementation simple. SWF only knows about "bold" and "normal". >>That's >> one reason SimpleCSSStylesImpl is "simple”. > >Is this a real concern? There are several other styles in that class that >don't have parity between JS and AS i.e background image, border style, >vertical align and padding. May also be others I’ve not looked at all >properties in detail. They may not have parity today due to bugs, but the goal is to reduce the differences to zero if possible. I think we can do that for the styles in there, and if we can't, we'll probably pull out the ones we can't. > >It seems wrong to me to disable something in the JS side just because >it’s not supported in the AS side. It isn't disabling something on the JS side, it is giving users choices about size, performance and features. That is the nature of PAYG. There is no one "right" answer. Users are not required to use SimpleCSSStylesImpl, and I doubt SimpleCSSStylesImpl will be the most popular IValuesImpl. But it has a goal of being "simple", small, and parity. We definitely need the code you wrote, but in a different class. We need other IValuesImpls. Thanks, -Alex
