Thanks for pointing out these concepts but can you be more concrete on how this can solve my problem listed above?
I know the @Share and @Import concepts and use them, but as far as I know I still have to set a additional shared style name in java code on the widget as explained above. This is something I don't want as the widget already has one style and the widget should be shared-style agnostic of course (suppose it's a shared style called SHARED to centered the widget). The only solution I see, is adding the Shared style to the @ClassName annotation, but that currently isn't possible. Looking forward to your reaction. - Ed Op maandag 16 juli 2012 15:31:25 UTC+2 schreef Abraham Lin het volgende: > > Why don't you define a CSSResource with the shared rules and import it > where needed? See > https://developers.google.com/web-toolkit/doc/latest/DevGuideClientBundle#Imported_scopes > (and > possibly > https://developers.google.com/web-toolkit/doc/latest/DevGuideClientBundle#Shared_scopes > depending > on your particular use case). > > On Monday, July 16, 2012 3:23:43 AM UTC-4, Ed wrote: >> >> Might it be an idea if the @ClassName annotation allows for an array of >> String value's (currently not possible)? >> This could solve the problems described above I think. Example: >> >> public interface WidgetStyle extends CssResource { >> @ClassName({"Bla", "General"}) >> String bla(); { >> } >> > > This should be equivalent to just adding multiple classes to the widget > itself. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/5ssyadDtQfAJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
