Hi,

Royale has been using the universal selector for a while now to set
defaults for Royale apps.  However, that caused problems with other
third-party CSS.

I just pushed changes to the compiler and framework so that we don't use
the * selector.  Instead we will be using the * selector properly if
provided by the users CSS and we are using a special selector called
"global" as the "browser defaults" and the final selector in the lookup we
manage.

This should eliminate the need for other component sets to try to exclude
the defaults.css from Basic.

You may find that text that once looked nice now is 16px Serif.  That's
because we are no longer using inheritance to set the font-family on all
components.  The browsers do not seem to deploy a default font-family so
the SWF side shouldn't either.  IOW, if you just put some plain text in an
HTML file it shows up as 16px Serif.  If you see 16px Serif, let us know
which component is showing that by default.

However, we don't really want to make 16px Serif the default font in our
examples, so I created a CSS-based theme in themes/Basic/basic.css and put
12px Sans-Serif as the default for a bunch of type selectors since that
was what our examples were using.  I did not create a default font for
Application as that would become the default for other component sets
mixed into a Royale app unless otherwise specified.  Component sets with
different looks can use a different theme and get different defaults.

So, in sum, without any theme, we want the SWF side to look like the
browser and have 16px Serif.  But the royale-config.xml will specify
themes/Basic/basic.css as the default theme giving the examples and most
people's unstyled apps a more Flex-like look by using sans-serif.  More
type selectors may need to be added to themes/Basic/basic.css in order to
get sans serif everywhere by default without putting font-family on
Application.  That way, when you switch to another theme, like the Vivid
that Carlos is working on, there should be fewer, if any, default values
that screw up the other theme.

Thanks,
-Alex

Reply via email to