My understanding was that ClientBundle could be used to create a global-type style/image package that would be delivered when needed. I am not sure that is a correct interpretation. Let me explain my use-case:
1) I have an app with 3 implementations (Desktop/Mobile/Table). My hope was to have 3 client bundles that would each serve as the definition for all the images/styles needed in those implementations. 2) In each ui bindler file in a given implementation (for example, shell.ui.xml, viewX.ui.xml, etc.), I use the <ui:with field="resources" type ="...Resources" /> and their corresponding .java files each have members like: @UiField(provided = true) final Resources resources = GWT.create(Resources. class); 3) I call Resources.INSTANCE.style().ensureInjected() in the constructor of each "widget" class. 4) However, the styles that are ONLY used in viewX.ui.xml (that don't appear in shell.ui.xml) are never injected (presumably because the ensureInjected() is called for the shell and then each subsequent call is a no-op, per the docs). Am I missing the point of the ClientBundle? Would the proper thing to do be to define any styles specific to viewX in the viewX.ui.xml file using ui:style? Am I just using this incorrectly? -- 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/-/ju20VIgzvuUJ. 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.
