Digging through the forum did not help me a lot, so I found my way the hard way and thought that findings may be helpful to others and that Isomorphic may want to comment too.
And the findings are : dynamic theme switching in the enterprise edition seems to be kind of a catch 22 situation. The problem I encountered is that skins are only included in the build if they are inherited in the xxx.gwt.xml file but then they are also unconditionally loaded into the browser. Manual loading by javascript embedded in the html still works but loading all skins every time is redundant and kind of scary. If I inherit from com.smartgwtee.SmartGwtEENoTheme only and include no themes then everything works perfectly IF i copy manually the skins to sc/skins. It is of course wrong that desired behavior can only be achieved by manual intervention in the build process but this is how it seems to be. I am attaching FYI files from a modified example built-in-ds found in the EE distribution.
And the findings are : dynamic theme switching in the enterprise edition seems to be kind of a catch 22 situation. The problem I encountered is that skins are only included in the build if they are inherited in the xxx.gwt.xml file but then they are also unconditionally loaded into the browser. Manual loading by javascript embedded in the html still works but loading all skins every time is redundant and kind of scary. If I inherit from com.smartgwtee.SmartGwtEENoTheme only and include no themes then everything works perfectly IF i copy manually the skins to sc/skins. It is of course wrong that desired behavior can only be achieved by manual intervention in the build process but this is how it seems to be. I am attaching FYI files from a modified example built-in-ds found in the EE distribution.
Comment