Seth, Currently I can do this by setting <ui:style > src='<relativepath>/MyCss.css"> in A and B and it works nicely, uibinder > takes care of injecting the styles and everything. However I'm not sure if > this is the best way. There's also the issue that if I move A and B then > the relative path breaks (since absolute paths still aren't 100% functional > issue#7230<http://code.google.com/p/google-web-toolkit/issues/detail?id=7230>). > > Does anyone have a clue or is this the preferred method? >
You might want to look at this previous answer<https://groups.google.com/forum/?fromgroups#!searchin/google-web-toolkit/lust$20cssresource/google-web-toolkit/XDTiBioiIuo/ZFHeGB1jT0IJ>. If you do the overriding in the Java class backing your UI binder, then the refactoring worries won't be a problem. You can still handle the refactoring in UiBinder, but you'll have to set Eclipse (or IDE of choice) to do FQN replacements in all .xml files. Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
