Thursday, July 16, 2015

Re: How to re-brand a base project?

This article could help you: http://blog.arcbees.com/2015/04/28/managing-your-css-files-with-variables-and-a-theme/

On Wednesday, July 15, 2015 at 4:14:21 PM UTC+2, William Davis wrote:
I have a base application with all the functionality. Lets say I want to create several different versions for different organizations. Obviously each organization will want their own colors, styles, images, theme, etc in their respective version. My thought is to create a new module for each organization and inherit the base module in order to get all the functionality. Now what I need to do is to somehow inject, or override certain ClientBundles to provide specific style sheets and images. This is where I am not sure what the best approach would be. I thought that I could simply do a <replace-with> in the organization's module (.gwt.xml) file to swap out a different ClientBundle that has CssResources and ImageResources. However since the ClientBundles are interfaces that doesn't seem to work. Does anyone know of a good pattern to accomplish this? Is it possible to use deferred binding or Gin to provide different interfaces?

Thanks,
Will

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment