vinuriyer,
I'm not sure if it relevant to you now, just bumped into this thread searching for something else.
You can create a jar file of the theme with all your changes and use that as your application theme, so that you need not do changes to the war after every build.
This approach is handy if you wanted to share the same styling across solutions etc. But for the initial styling this is not recommended for the same obvious reasons you have mentioned. Needs to create the jar for every change you make.
The second approach that can be used to increase productivity is the approach mentioned in the last part of the Styling chapter in SmartGWT quick start guide. In this approach you never have to restart the server etc. You can just use Google development mode, the way you use for java changes.
Once you are done you can create a jar which can be distributed across solutions in a company.
Hope this helps.
Thanks.
I'm not sure if it relevant to you now, just bumped into this thread searching for something else.
You can create a jar file of the theme with all your changes and use that as your application theme, so that you need not do changes to the war after every build.
This approach is handy if you wanted to share the same styling across solutions etc. But for the initial styling this is not recommended for the same obvious reasons you have mentioned. Needs to create the jar for every change you make.
The second approach that can be used to increase productivity is the approach mentioned in the last part of the Styling chapter in SmartGWT quick start guide. In this approach you never have to restart the server etc. You can just use Google development mode, the way you use for java changes.
Once you are done you can create a jar which can be distributed across solutions in a company.
Hope this helps.
Thanks.
Comment