royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <>
Subject Re: Flex2Royale
Date Mon, 16 Oct 2017 16:04:48 GMT
IIRC, Om was working on this to some degree.  One plan was to convert FXG
to SVG.

AIUI, a SkinnableContainer wouldn't be that hard.  Container already has
an inner div to hold the children, so a different view could have the
outer div display SVG behind the children.  I think there were more
questions about SkinnableComponent because not every component is already
implemented to support a skin by default, and SVG as a backgroundImage for
some HTMLElements don't work well in all browsers.

Flex Skinning was pretty expensive because it added a UIComponent child to
every component.  Because we are PAYG, we don't want to force that on
everyone, and as the MDL work showed, CSS Themes may be just as good at
creating nice visual experiences and more standard/common.  But as Yishay
said, in theory, a new set of views could add that extra DIV behind each
component if that's what it takes to implement SVG "skins".  And we also
know from MDL and Flat that we can also just re-factor components into
enough pieces that they can have a different look.

Of course, I could be wrong...

On 10/16/17, 6:50 AM, "Peter Ent" <> wrote:

>We need to have a "skinning story" - something about alternate views, CSS,
>that sort of thing. Adding to my list.
>On 10/16/17, 2:29 AM, "yishayw" <> wrote:
>>I like it.
>>> There is no direct equivalent of SkinnableContainer in Royale (at this
>>> time). A reasonable alternative is the Container.
>>Maybe we could mention that Royale components typically have views which
>>be used to control appearance without changing behavior. To me, spark
>>sort of played the same role.
>>Sent from: 

View raw message