Just to be clear:
In the case at hand, where the shared CSS file has nothing in it but @def
values, there is nothing to be gained by an approach that is any more
complicated than:
<ui:style src='colors.css'>
.foo { color: yellow; }
</ui:style>
But if you want to share actual class definitions, the @Shared mixin is the
way to go.
On Wed, Nov 18, 2009 at 6:07 AM, BobV <[email protected]> wrote:
> > @bobv, will anything pathological happen to the generated code if lots of
> > ui.xml files all do this? Remember that each ui.xml defines its own
> > ClientBundle.
>
> The common css will be duplicated every time you do this, but this may
> be what you want, depending on whether or not the common css should be
> shared between the widget types at runtime. If the common css can be
> reused, you would be better off creating an @Shared CssResource for
> the common CSS and then having the per-UI.xml CssResource mix in the
> additional rules.
>
> --
> Bob Vawter
> Google Web Toolkit Team
>
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
